Re: [Gcl-devel] gcc3.x (does gcl-2.4.3 or gcl-cvs) build with gcc3.x

[Camm Maguire]

Greetings, and thanks for the heads up.

address@hidden writes:

> Hi,
> 
> I have big problems compiling gcl-2.4.3 (or gcl-cvs) with gcc 3.3 (cvs)
> 
> first the file gmp/longlong.h has asm-inline statements which are no
> longer recognized by gcc-3.x.
> Fixing that  I get lateron

I hope its the 'inline' and not the 'asm' which is not supported.  Can
you clarify?


> 
> Entering directory `/OBJ/GCL/gcl-2.4.3/o'
> gcc -pipe -fwritable-strings  -DVOL=volatile -I/OBJ/GCL/gcl-2.4.3/o 
> -fsigned-char -c -O  -I../gcl-tk -I../h/ -O4   main.c  
> In file included from ../h/compbas.h:3,
>                  from ../h/include.h:60,
>                  from main.c:38:
> /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3/include/varargs.h:4:2: #error 
> "GCC no longer implements <varargs.h>."
> /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3/include/varargs.h:5:2: #error 
> "Revise your code to use <stdarg.h>."

I'm hoping here that the released gcc will support varargs.  You can't
pass all arguments in a va_list with stdarg, so this will force gcl to
rewrite its compiler to insert a dummy arg into every function, or
almost every one.  What possible advantage could there be in forcing
all vararg users to rewrite their code?  this must be a temporary cvs
issue, no?

> main.c:589: error: parse error before "va_dcl"
> main.c:590: error: syntax error before '{' token
> main.c:592: error: parse error before "ap"
> main.c:592: warning: data definition has no type or storage class
> main.c:601: warning: parameter names (without types) in function declaration
> main.c:601: warning: data definition has no type or storage class
> main.c:604: error: parse error before "do"
> main.c:604: error: parse error before numeric constant
> main.c:609: error: parse error before "va_dcl"
> main.c:610: error: syntax error before '{' token
> main.c:614: error: parse error before "va_dcl"
> main.c:615: error: syntax error before '{' token
> make[1]: *** [main.o] Error 1
> make[1]: Leaving directory `/OBJ/GCL/gcl-2.4.3/o'
> make: *** [all] Error 2
> 
> Trying to build with gcc-2.95.3 fails as well since
> then incompatibilies with my system libbfd.a :
> 
> /usr/lib/libbfd.a(srec.o): In function `srec_bad_byte':
> /Src/OBJ/binutils-build/bfd/../../binutils-2.12/bfd/srec.c:293: undefined 
> reference to `_sch_istable'
> /usr/lib/libbfd.a(srec.o): In function `srec_scan':
> /Src/OBJ/binutils-build/bfd/../../binutils-2.12/bfd/srec.c:419: undefined 
> reference to `_sch_istable'
> 

This symbol should be in your libiberty.a.  Could you please check
with 'nm libiberty.a |grep _sch_istable"?


> and so on
> 
> (Note my system is build by gcc-3.x from bottom up)
> 
> So, what can I do to build gcl ?
> 

The vararg bit will take considerable work.  So for now you should use
a released gcc.

Take care,


> Thanks for any hints,
> 
> Helmut Jarausch
> 
> Lehrstuhl fuer Numerische Mathematik
> Institute of Technology, RWTH Aachen
> D 52056 Aachen, Germany
> 
> 
> _______________________________________________
> Gcl-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gcl-devel
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah