From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Compiling Gnus under MS Windows
Date: Fri, 07 Sep 2001 02:54:40 -0400 [thread overview]
Message-ID: <2nvgivh4nj.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <7kvczdeu.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Thu, 06 Sep 2001 14:55:53 +0200")
Frank Schmitt <Azzrael@rz-online.de> writes:
> When trying to do make under cygwin (configure works like a charm) I get
> the following output:
>
> $ make emacs=xemacs
> cd lisp && make EMACS="xemacs" lispdir="/cygdrive/c/Programme/XEmacs/XEmacs-21.4.3/share/xemacs/site-lisp" all
> make[1]: Entering directory `/cygdrive/c/Programme/XEmacs/XEmacs-21.4.3/i586-pc-win32/gnus-CURRENT-20010906/lisp'
> rm -f *.elc gnus-load.el
> f dgnushack-make-cus-load .
> f: not found
> make[1]: [gnus-load.elc] Error 127 (ignored)
> f dgnushack-make-auto-load .
> f: not found
> make[1]: [gnus-load.elc] Error 127 (ignored)
> f dgnushack-make-load
> f: not found
> make[1]: [gnus-load.elc] Error 127 (ignored)
> f dgnushack-compile
> f: not found
> make[1]: [all] Error 127 (ignored)
> make[1]: Leaving directory `/cygdrive/c/Programme/XEmacs/XEmacs-21.4.3/i586-pc-win32/gnus-CURRENT-20010906/lisp'
> cd texi && make EMACS="xemacs" all
> make[1]: Entering directory `/cygdrive/c/Programme/XEmacs/XEmacs-21.4.3/i586-pc-win32/gnus-CURRENT-20010906/texi'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/cygdrive/c/Programme/XEmacs/XEmacs-21.4.3/i586-pc-win32/gnus-CURRENT-20010906/texi'
>
> What does this mean?
It looks like that EMACS_COMP in Makefile expands to an empty string.
I can't figure out why.
ShengHuo
next prev parent reply other threads:[~2001-09-07 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 12:55 Frank Schmitt
2001-09-07 6:54 ` ShengHuo ZHU [this message]
2001-09-07 13:34 ` Frank Schmitt
2001-09-18 11:53 ` Frank Schmitt
2001-09-19 3:02 ` ShengHuo ZHU
2001-09-19 10:36 ` David Maslen
2001-09-19 11:09 ` Frank Schmitt
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=2nvgivh4nj.fsf@piglet.jia.vnet \
--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).