Andy Piper writes:
At 03:49 PM 2/23/01 +0000, Philip Aston wrote:
>Problem 1
>*********
>
> $ cvs -d :pserver:xemacs@cvs.xemacs.org:/usr/CVSroot
> checkout -rr21-2-latest-beta xemacs
> $ pwd
> $ cd xemacs/
> $ ./configure
> $ make
>
>craps out not being able to find the win32 api:
>
> make[1]: Entering directory
> `/usr/local/src/xemacs-21.2-temp/xemacs/netinstall'
> gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wshadow
> -Wpointer-arith -O2 -DMINGW -I/usr/lib/../include/mingw32
> -I/usr/lib/../include/mingw -I/usr/lib/../include -mno-cygwin -I.
> -I/usr/local/src/xemacs-21.2-temp/xemacs/netinstall -mwindows -c -o
> autoload.o /usr/local/src/xemacs-21.2-temp/xemacs/netinstall/autoload.c
> In file included from
> /usr/local/src/xemacs-21.2-temp/xemacs/netinstall/autoload.c:16:
> /usr/local/src/xemacs-21.2-temp/xemacs/netinstall/win32.h:34: windef.h:
> No such file or directory
> /usr/local/src/xemacs-21.2-temp/xemacs/netinstall/win32.h:35:
> basetyps.h: No such file or directory
I fixed this a while ago - and it works for me with the latest cygwin
snapshot. Make sure you have win32 and mingw installed. Also make sure you
have rerun configure.
I have the latest snapshot, win32, and mingw. I ran configure from a
clean build, see above.
>et cetera. I _think_ this is a gcc bug and that -mwindows should
>automatically add the w32api directory to the include path.
>
>make -k shows similar problems with compiling ./src
>
>So I say
>
> $ ./configure --site-includes=/usr/include/w32api
>
>No joy for netinstall (--site-includes doesn't make it to its
>makefile, should it?), but this works for src.
>
>
>Problem 2
>*********
>
>The second problem seems more subtle. When doing a build from a clean
>cvs tree (as above), temacs spins when batch compiling the lisp.
>
>Compiling explicitly with:
>
> $ xemacs -batch -q -no-site-file -l bytecomp -f batch-byte-compile
> /usr/local/src/xemacs-21.2-temp/xemacs/lisp/*.el
>
>works. Then the make completes fine. Any hints on debugging this?
I've sometimes seen this. Killing and restarting seems to cure :)
Not for me. Tried many times.
- Phil
-------------------------------------------
Philip Aston - Senior Consultant
BEA Professional Services (Northern Europe)