From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: compiling Oort Gnus 0.05
Date: Thu, 07 Feb 2002 18:29:43 -0500 [thread overview]
Message-ID: <2neljw98go.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <ug04clxhg.fsf@webmethods.com> (dnc@bigfoot.com's message of "07 Feb 2002 14:48:27 -0800")
dnc@bigfoot.com writes:
> I hate to be the guy asking the "how do I compile this?" question, but
> here goes anyway...
>
> I just downloaded Oort Gnus 0.05, and I want to compile/install it for
> xemacs. I've done what I thought would work, namely
>
> ./configure --with-xemacs
> make EMACS=xemacs
>
> The make command fails, with the output shown below. Before I get to
> that, some version information. I'm on Windows 2000 Professional,
> using the cygwin tools (make, bash, etc...). Version numbers here:
[...]
> I've figured out that the gnus-load.el target is failing in
> ognus-0.05/lisp/. It seems that the EMACS_COMP variable is not being
> defined properly. So instead of running
> $(EMACS_COMP) -f dgnushack-make-cus-load $(srcdir)
> It runs only
> -f dgnushack-make-cus-load $(srcdir)
>
> And thus I see the message
> f: not found
>
> Does anyone know why this is happening? Is it the cygwin tools? How,
> if at all, is ognus normally built on a Windows machine?
This was reported before. The problem is the mixture of forward
slashes and backslashes. XEmacs reports backslashes in paths, but
make doesn't handle it. Maybe make-x.bat does a better job.
ShengHuo
prev parent reply other threads:[~2002-02-07 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 22:48 dnc
2002-02-07 23:29 ` ShengHuo ZHU [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2neljw98go.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).