Gnus development mailing list
 help / color / mirror / Atom feed
* Compiling Gnus under MS Windows
@ 2001-09-06 12:55 Frank Schmitt
  2001-09-07  6:54 ` ShengHuo ZHU
                   ` (2 more replies)
  0 siblings, 3 replies; 7+ messages in thread
From: Frank Schmitt @ 2001-09-06 12:55 UTC (permalink / raw)


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?

Afterwards I tried to use the make.bat but this one only works with GNU
Emacs, not with XEmacs. I changed it so it would search for xemacs.exe
if it can't find emacs.exe and it seems that it worked, (at least I'm
now writing in my brandnew snapshot oort gnus) but I don't really know
if really everything is ok now.

Well in fact what I wanted to say was: There's now obvious way to
compile Gnus under Window and XEmacs, this must be changed.

-- 
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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Compiling Gnus under MS Windows
  2001-09-06 12:55 Compiling Gnus under MS Windows Frank Schmitt
@ 2001-09-07  6:54 ` ShengHuo ZHU
  2001-09-07 13:34   ` Frank Schmitt
  2001-09-18 11:53 ` Frank Schmitt
  2001-09-19 10:36 ` David Maslen
  2 siblings, 1 reply; 7+ messages in thread
From: ShengHuo ZHU @ 2001-09-07  6:54 UTC (permalink / raw)


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Compiling Gnus under MS Windows
  2001-09-07  6:54 ` ShengHuo ZHU
@ 2001-09-07 13:34   ` Frank Schmitt
  0 siblings, 0 replies; 7+ messages in thread
From: Frank Schmitt @ 2001-09-07 13:34 UTC (permalink / raw)


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Compiling Gnus under MS Windows
  2001-09-06 12:55 Compiling Gnus under MS Windows Frank Schmitt
  2001-09-07  6:54 ` ShengHuo ZHU
@ 2001-09-18 11:53 ` Frank Schmitt
  2001-09-19  3:02   ` ShengHuo ZHU
  2001-09-19 10:36 ` David Maslen
  2 siblings, 1 reply; 7+ messages in thread
From: Frank Schmitt @ 2001-09-18 11:53 UTC (permalink / raw)


Frank Schmitt <Azzrael@rz-online.de> writes:

>When trying to do make under cygwin (configure works like a charm) I get
>the following output:
[well, it's broken]
>What does this mean?
>
>Afterwards I tried to use the make.bat but this one only works with GNU
>Emacs, not with XEmacs. I changed it so it would search for xemacs.exe
>if it can't find emacs.exe and it seems that it worked, (at least I'm
>now writing in my brandnew snapshot oort gnus) but I don't really know
>if really everything is ok now.
>
>Well in fact what I wanted to say was: There's now obvious way to
>compile Gnus under Window and XEmacs, this must be changed.

Does this really not interest the maintainers of Gnus? At least it
should be possible to update the make.bat, so it works with XEmacs,
too. I would be willing to do this if one would tell me which
instruction have to be carried out and in which places the compilation
under XEmacs differs from compilation under Gnu Emacs.

-- 
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.
20. Dezember 2001


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Compiling Gnus under MS Windows
  2001-09-18 11:53 ` Frank Schmitt
@ 2001-09-19  3:02   ` ShengHuo ZHU
  0 siblings, 0 replies; 7+ messages in thread
From: ShengHuo ZHU @ 2001-09-19  3:02 UTC (permalink / raw)


Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:

> Frank Schmitt <Azzrael@rz-online.de> writes:
>
>>When trying to do make under cygwin (configure works like a charm) I get
>>the following output:
> [well, it's broken]
> >What does this mean?
>>
>>Afterwards I tried to use the make.bat but this one only works with GNU
>>Emacs, not with XEmacs. I changed it so it would search for xemacs.exe
>>if it can't find emacs.exe and it seems that it worked, (at least I'm
>>now writing in my brandnew snapshot oort gnus) but I don't really know
>>if really everything is ok now.
>>
>>Well in fact what I wanted to say was: There's now obvious way to
>>compile Gnus under Window and XEmacs, this must be changed.
>
> Does this really not interest the maintainers of Gnus? 

It is interesting, but I don't play M$ Windows much.

> At least it should be possible to update the make.bat, so it works
> with XEmacs, too.

I've added make-x.bat into the Gnus CVS.

> I would be willing to do this if one would tell me which instruction
> have to be carried out and in which places the compilation under
> XEmacs differs from compilation under Gnu Emacs.

Another solution is to run nmake xemacs.mak.

Yet another solution is to manually change backslash to forward slash
in Makefile.

Hope these help.

ShengHuo


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Compiling Gnus under MS Windows
  2001-09-06 12:55 Compiling Gnus under MS Windows Frank Schmitt
  2001-09-07  6:54 ` ShengHuo ZHU
  2001-09-18 11:53 ` Frank Schmitt
@ 2001-09-19 10:36 ` David Maslen
  2001-09-19 11:09   ` Frank Schmitt
  2 siblings, 1 reply; 7+ messages in thread
From: David Maslen @ 2001-09-19 10:36 UTC (permalink / raw)


I built xemacs-21.5-b0 under cygwin today. 
I simple ran ./configure --with-sound=no 

Seems to work fine, except I don't think I have all the additional
graphic libraries installed as the tool bar looks pretty much black
and white. I don't display the tool bar anyhow, so not a problem from
my point of view.

I also built oort gnus 0.03, which worked fine too.

One rather strange problem, which is probably just my lack of xemacs
knowledge. is that despite the fact I have added the
/usr/lib/xemacs/site-lisp/ and despite the fact that that
locate-library and load-library both find gnus.el, M-x gnus doesn't
find a correct completion.

I seem to have got around the problem by putting (require 'gnus) in
my xemacs init.el file. Is there a better way to do this? 


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Compiling Gnus under MS Windows
  2001-09-19 10:36 ` David Maslen
@ 2001-09-19 11:09   ` Frank Schmitt
  0 siblings, 0 replies; 7+ messages in thread
From: Frank Schmitt @ 2001-09-19 11:09 UTC (permalink / raw)


David Maslen <dmm@trinity.home.private> writes:

>I built xemacs-21.5-b0 under cygwin today. 
>I simple ran ./configure --with-sound=no 

I am talking about compiling gnus under a running xemacs. I am not
talking about how to compile xemacs. That's off-topic here.

-- 
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.
20. Dezember 2001


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2001-09-19 11:09 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-09-06 12:55 Compiling Gnus under MS Windows Frank Schmitt
2001-09-07  6:54 ` ShengHuo ZHU
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

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).