Re: libio compilation failure, i386-pc-linux-gnu

[hjl at lucon dot org (H.J. Lu)]

> 
> Mostly stock Red Hat Linux 4.2.
> 
> The main part of the build goes OK, but the libio stuff bombs.
> 
> test -z "-fpic" || \
>   /usr/src/redhat/BUILD/egcs-971114/gcc/xgcc
> -B/usr/src/redhat/BUILD/egcs-971114/gcc/ -c -g -O2 -fno-implicit-templates
> -I. -I. -nostdinc++ -D_IO_MTSAFE_IO -fpic stdstrbufs.cc -o
> pic/stdstrbufs.o
> stdstrbufs.cc:67: syntax error before `='
> stdstrbufs.cc:67: `_IO_stdfile_0_lock' was not declared in this scope
> stdstrbufs.cc:67: warning: excess elements in aggregate initializer
> stdstrbufs.cc:68: syntax error before `='
> stdstrbufs.cc:68: `_IO_stdfile_1_lock' was not declared in this scope
> stdstrbufs.cc:68: warning: excess elements in aggregate initializer
> stdstrbufs.cc:69: syntax error before `='
> stdstrbufs.cc:70: `_IO_stdfile_2_lock' was not declared in this scope
> stdstrbufs.cc:70: warning: excess elements in aggregate initializer
> make[1]: *** [stdstrbufs.o] Error 1
> make[1]: Leaving directory
> `/usr/src/redhat/BUILD/egcs-971114/libraries/libio'
> make: *** [all-target-libio] Error 2
> 

Please don't specify the target name when you configure egcs unless
you know exactly what you are doing. egcs will try to detect what
you have if you don't specify the target name. If you do, egcs won't
try. But if you don't know what's your target name in egcs's term
and you provide one, egcs is screwed.

BTW, is that in INSTALL/FAQ?



-- 
H.J. Lu (hjl@gnu.ai.mit.edu)