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

Re: cross-gcc status

> /home/me/gcc-3.3-3.3.5/build/gcc/xgcc
> -B/home/me/gcc-3.3-3.3.5/build/gcc/ -B/usr/powerpc-linux/bin/
> -B/usr/powerpc-linux/lib/ -isystem /usr/powerpc-linux/include -O2
> -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT
> -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I.
> -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config
> -I../../src/gcc/../include  -DL_muldi3 -c ../../src/gcc/libgcc2.c -o
> libgcc/./_muldi3.o
> In file included from tconfig.h:22,
>                   from ../../src/gcc/libgcc2.c:36:
> ../../src/gcc/config/rs6000/linux.h:96:20: signal.h: No such file or
> directory
> make[4]: *** [libgcc/./_muldi3.o] Error 1
> make[4]: Leaving directory `/home/me/gcc-3.3-3.3.5/build/gcc'
> make[3]: *** [stmp-multilib] Error 2
> make[3]: Leaving directory `/home/me/gcc-3.3-3.3.5/build/gcc'
> make[2]: *** [all-gcc] Error 2
> make[2]: Leaving directory `/home/me/gcc-3.3-3.3.5/build'
> s=`cat status`; rm -f status; test $s -eq 0
> make[1]: *** [stamps/05-build-stamp] Error 1
> make[1]: Leaving directory `/home/me/gcc-3.3-3.3.5'
> make: *** [stamps/05-build-stamp] Error 2
> Exit 2

Hmm... Just re-tested, with exact your dependent package versions. Builds ok
for me.

The mentioned 'signal.h' should be in /usr/powerpc-linux/include/, provided
by libc6-dev-powerpc-cross package.

Is the file there?

Have you downloaded libc6-dev-powerpc-cross package, or built it yourself
with dpkg-cross -b? Maybe you've built it with non-default path
configuration? (I guess dpkg-cross should name created package differently
if non-default paths are used...)

If file is really in /usr/powerpc-linux/include/signal.h, but you are
getting the above error, it's strange. In this case, please go
to /home/me/gcc-3.3-3.3.5/build/gcc, and run there the failing command,
adding '-v' switch, and show me the result.

Thank you for your feedback.


Reply to: