This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libio compilation failure, i386-pc-linux-gnu
- To: hjl at lucon dot org (H.J. Lu)
- Subject: Re: libio compilation failure, i386-pc-linux-gnu
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 19 Nov 1997 22:42:09 -0800
- cc: sopwith at cuc dot edu (Elliot Lee), egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <m0xYFCA-0004ecC@ocean.lucon.org>you write:
> >
> > 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-template
> s
> > -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
[ ... ]
> 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?
I didn't see any indication that Elliot specified a triplet at configure time,
but I could have missed it in the first message.
Elliot -- did you use "configure" or did you use "configure <somename>"?
HJ -- I'm not sure this belongs in an FAQ, but it certainly does belong in
the basic installation instructions.
jeff
>