gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] build errors with gcc 3.1


From: David Shochat
Subject: [Gcl-devel] build errors with gcc 3.1
Date: Fri, 26 Jul 2002 20:32:11 -0400
User-agent: Pan/0.12.91 (If you were in the moccasins of Peter Pigeonhole)

On 7/6, I posted build problems I got trying to build gcl 2.4.3 
using the compiler (gcc 2.96-110) that comes with RedHat Linux 7.3. 
Thanks to a helpful response from Camm Maguire, I was able to get 
it to build with a minor code change. The resulting gcl worked fine 
except that when I tried to use it with ilisp, emacs froze and had 
to be killed. I reported this on comp.lang.lisp and ilisp-help, but 
got no response from either.

So I thought I would try building with gcc 3.1. Again, I get a build 
error:

gcc3 -pipe -fwritable-strings  -DVOL=volatile 
 -I/usr/local/lisp/gcl/gcl-2.4.3/o -fsigned-char -c -O  
 -I../gcl-tk -I../h/ -O4   sfasl.c  
In file included from ../h/include.h:62,
                 from sfasl.c:40:
../h/object.h:67: warning: useless keyword or type name in empty 
 declaration
../h/object.h:67: warning: empty declaration
In file included from ../h/include.h:72,
                 from sfasl.c:40:
../h/att_ext.h:208: conflicting types for `GBC_enable'
../h/notcomp.h:9: previous declaration of `GBC_enable'
../h/att_ext.h:284: conflicting types for `initflag'
../h/notcomp.h:15: previous declaration of `initflag'
In file included from sfaslelf.c:273,
                 from sfasl.c:45:
sfaslelf.c: In function `fasload':
sfaslelf.c:136: warning: passing arg 0 of `round_up' makes 
 integer from pointer without a cast
make[1]: *** [sfasl.o] Error 1

So I decided to try latest cvs. In this case, I get a different 
build error:

make[1]: Entering directory `/usr/local/lisp/gcl/cvs/gcl/unixport'
make[1]: *** No rule to make target `../mp/libmport.a', 
 needed by `raw_gcl'.  Stop.
make[1]: Leaving directory `/usr/local/lisp/gcl/cvs/gcl/unixport'
make: *** [all] Error 2

Is there a known problem building gcl with gcc 3.1? Is current CVS 
unstable?

Thanks.
-- David






reply via email to

[Prev in Thread] Current Thread [Next in Thread]