Gnus development mailing list
 help / color / mirror / Atom feed
From: Frank Schmitt <Azzrael@rz-online.de>
Subject: Re: Compiling Gnus under MS Windows
Date: Fri, 07 Sep 2001 15:34:49 +0200	[thread overview]
Message-ID: <ae07w2di.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <2nvgivh4nj.fsf@piglet.jia.vnet>

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

>It looks like that EMACS_COMP in Makefile expands to an empty string.
>I can't figure out why.

Here's ./lisp/Makefile:

# Generated automatically from Makefile.in by configure.
datadir = ${prefix}/share
lispdir = $(datadir)/xemacs/site-lisp
prefix = c:\Programme\XEmacs\XEmacs-21.4.3
srcdir = .
subdir = lisp
top_srcdir = ..

EMACS = xemacs
FLAGS = -batch -q -no-site-file -l $(srcdir)/dgnushack.el
INSTALL = /usr/bin/install -c
INSTALL_DATA = ${INSTALL} -m 644
SHELL = /bin/sh
W3DIR = c:\Programme\XEmacs\xemacs-packages\lisp\w3\
URLDIR = c:\Programme\XEmacs\xemacs-packages\lisp\w3\
EMACS_COMP = URLDIR=$(URLDIR) W3DIR=$(W3DIR) lispdir=$(lispdir) srcdir=$(srcdir) $(EMACS) $(FLAGS)

all total: clean-some gnus-load.elc
	$(EMACS_COMP) -f dgnushack-compile

clean-some:
	rm -f *.elc gnus-load.el

warn: clean-some gnus-load.elc
	$(EMACS_COMP) --eval '(dgnushack-compile t)' 2>&1 | egrep -v "variable G|inhibit-point-motion-hooks|coding-system|temp-results|variable gnus|variable nn|scroll-in-place|deactivate-mark|filladapt-mode|byte-code-function-p|print-quoted|ps-right-header|ps-left-header|article-inhibit|print-escape|ssl-program-arguments|message-log-max"

# The "clever" rule is unsafe, since redefined macros are loaded from
# .elc files, and not the .el file.
clever some: gnus-load.elc
	$(EMACS_COMP) -f dgnushack-compile

install: clever
	rm -f dgnushack.elc
	$(SHELL) $(top_srcdir)/mkinstalldirs $(lispdir)
	for p in *.elc; do \
	  echo " $(INSTALL_DATA) $$p $(lispdir)/$$p"; \
	  $(INSTALL_DATA) $$p $(lispdir)/$$p; \
	done

install-el:
	$(SHELL) $(top_srcdir)/mkinstalldirs $(lispdir)
	cd $(srcdir) \
	&& for p in *.el; do \
	  echo " $(INSTALL_DATA) $$p $(lispdir)/$$p"; \
	  $(INSTALL_DATA) $$p $(lispdir)/$$p; \
	done

tags:
	etags *.el

separately:
	rm -f *.elc ; for i in *.el; do $(EMACS) $(FLAGS) -f batch-byte-compile $$i; done

pot:
	xpot -drgnus -r`cat ./version` *.el > rgnus.pot

gnus-load.elc:
	$(EMACS_COMP) -f dgnushack-make-cus-load $(srcdir)
	$(EMACS_COMP) -f dgnushack-make-auto-load $(srcdir)
	$(EMACS_COMP) -f dgnushack-make-load

distclean:
	rm -f *.orig *.rej *.elc *~ Makefile

Makefile: $(srcdir)/Makefile.in ../config.status
	cd .. \
	  && CONFIG_FILES=$(subdir)/$@ CONFIG_HEADERS= $(SHELL) ./config.status

# Tell versions [3.59,3.63) of GNU make to not export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:


-- 
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
19. Dezember 2001


  reply	other threads:[~2001-09-07 13:34 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
2001-09-07 13:34   ` Frank Schmitt [this message]
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=ae07w2di.fsf@hschmi22.userfqdn.rz-online.de \
    --to=azzrael@rz-online.de \
    /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).