This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: build problems on powerpc.
- From: Phil Edwards <phil at jaj dot com>
- To: Nic Ferrier <nferrier at tapsellferrier dot co dot uk>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Tue, 9 Jul 2002 12:44:28 -0400
- Subject: Re: build problems on powerpc.
- References: <87lm8lq36z.fsf@pooh-sticks-bridge.tapsellferrier.co.uk>
On Mon, Jul 08, 2002 at 11:12:36PM +0100, Nic Ferrier wrote:
> The build error occurs whilst doing this:
>
> /home/nferrier/projects/gnu/gcc/cvsobj/gcc/xgcc -shared-libgcc -B/home/nferrier/projects/gnu/gcc/cvsobj/gcc/ -nostdinc++ -L/home/nferrier/projects/gnu/gcc/cvsobj/powerpc-unknown-linux-gnu/libstdc++-v3/src -L/home/nferrier/projects/gnu/gcc/cvsobj/powerpc-unknown-linux-gnu/libstdc++-v3/src/.libs -B/usr/local/powerpc-unknown-linux-gnu/bin/ -B/usr/local/powerpc-unknown-linux-gnu/lib/ -isystem /usr/local/powerpc-unknown-linux-gnu/include -nostdinc++ -I/home/nferrier/projects/gnu/gcc/cvsobj/powerpc-unknown-linux-gnu/libstdc++-v3/include/powerpc-unknown-linux-gnu -I/home/nferrier/projects/gnu/gcc/cvsobj/powerpc-unknown-linux-gnu/libstdc++-v3/include -I../../../../gccstable-cvs/libstdc++-v3/libsupc++ -I../../../../gccstable-cvs/libstdc++-v3/libmath -g -O2 -D_GNU_SOURCE -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -c ../../../../gccstable-cvs/libstdc++-v3/src/complex_io.cc -o complex_io.o >/dev/null 2>&1
>
>
> Here's the error text produced by the Makefile:
>
> make[3]: *** [complex_io.lo] Error 1
Unfortunately this doesn't tell us /what/ went wrong, only that compilation
failed. The error message from the compiler is sent to /dev/null, as you
can see from the command invocation. (This is supposed to be a libtool
feature; there are arguments and reasons for and against in the main gcc
list archives if you're curious and bored.)
The upshot is that compiling complex_io.cc worked with -fPIC -DPIC, but
failed without it. That usually points to a target-specific compiler bug,
but you'll have to run that command by hand, without the ">/dev/null 2>&1"
at the end, to see the error messages.
Ideally --enable-maintainer-mode would make the /dev/null bit go away, but
we don't have that much control over libtool.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams