compiling Oort Gnus 0.05

compiling Oort Gnus 0.05

[dnc]

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:

> bash --version
GNU bash, version 2.05.0(6)-release (i686-pc-cygwin)
Copyright 2000 Free Software Foundation, Inc.
//c/tmp
> make --version
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for i686-pc-cygwin

Xemacs is version 21.4.3

Now, I type './configure --with-xemacs' and it works fine...

> ./configure --with-xemacs
creating cache ./config.cache
checking whether make sets ${MAKE}... no
checking for a BSD compatible install... /usr/bin/install -c
checking for makeinfo... makeinfo
checking for emacs... xemacs
checking if xemacs is really XEmacs... yes
checking prefix for your Emacs... c:\install\xemacs\XEmacs-21.4.3
checking where .elc files should go... $(datadir)/xemacs/site-lisp
checking where etc files should go... $(lispdir)/../etc
checking for acceptable URL version... c:\install\xemacs\xemacs-packages\lisp\w3
\
checking for acceptable W3 version... c:\install\xemacs\xemacs-packages\lisp\w3\

checking for latex... /usr/bin/latex
checking for available fonts... no
updating cache ./config.cache
creating ./config.status
creating Makefile
creating etc/Makefile
creating lisp/Makefile
creating texi/Makefile
creating texi/gnusconfig.tex
creating texi/ps/Makefile




Next I type 'make EMACS=xemcs' (I think the "EMACS=xemacs" is not
truly necessary).  And it fails:



> make EMACS=xemacs
cd lisp && make EMACS="xemacs" lispdir="c:\install\xemacs\XEmacs-21.4.3/share/xe
macs/site-lisp" all
make[1]: Entering directory `//c/install/emacsStuff/ognus-0.05/lisp'
rm -f *.elc gnus-load.el
f dgnushack-make-cus-load .
f: not found
make[1]: [gnus-load.el] Error 127 (ignored)
f dgnushack-make-auto-load .
f: not found
make[1]: [gnus-load.el] Error 127 (ignored)
f dgnushack-make-load
f: not found
make[1]: [gnus-load.el] Error 127 (ignored)
f dgnushack-compile
f: not found
make[1]: [all] Error 127 (ignored)
make[1]: Leaving directory `//c/install/emacsStuff/ognus-0.05/lisp'
cd texi && make EMACS="xemacs" all
make[1]: Entering directory `//c/install/emacsStuff/ognus-0.05/texi'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `//c/install/emacsStuff/ognus-0.05/texi'




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?

My apologies if any part of this email is a FAQ.

And thanks for any help.

-Dave

Re: compiling Oort Gnus 0.05

[ShengHuo ZHU]

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