cross compile to arm-wrs-vxworks fails internal error
Sean McNeil
sean@mcneil.com
Tue Jun 13 19:44:00 GMT 2000
By the way, I've noticed that it is no longer possible to compile a cross
compiler from an unpriveleged account that is to be installed into a
priveleged account. For instance, I usually compile in my user account
then su root and install. Can't do this with a cross compiler anymore
because it tries to build some things directly into $prefix/lib/....
Sean McNeil wrote:
> Hi,
>
> I'm compiling with the following:
>
> current cvs as of today.
> host is i686-pc-linux-gnu latest kernel
> compiler is built from same source with "make bootstrap".
> configured simply with ../configure --prefix=/usr
> --target=arm-wrs-vxworks
> using tornado 2.01 include files with one mod in types/vxTypesBase.h to
> define __GNUC_TYPEOF_FEATURE_BROKEN_USE_DEFAULT_UNTIL_FIXED__ (this
> actually works backwards and says "yes, typeof feature works")
>
> I get the following message:
>
> /users/sean/gcc/gcc/arm-wrs-vxworks/gcc/xgcc
> -B/users/sean/gcc/gcc/arm-wrs-vxworks/gcc/ -B/usr/arm-wrs-vxworks/bin/
> -I/usr/arm-wrs-vxworks/include -O2 -DCROSS_COMPILE -DIN_GCC -g -O2
> -isystem ./include -Dinhibit_libc -fno-inline -g1 -DHAVE_GTHR_DEFAULT
> -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -g -O2 -I.
> -I../../gcc -I../../gcc/config -I../../gcc/../include \
> -c ../../gcc/cp/tinfo.cc
> In file included from ../../gcc/cp/tinfo.cc:33:
> ../../gcc/cp/tinfo.h:203: Internal compiler error 73.
> ../../gcc/cp/tinfo.h:203: Please submit a full bug report.
> ../../gcc/cp/tinfo.h:203: See
> <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
> make[3]: *** [tinfo.o] Error 1
> make[3]: Leaving directory `/users/sean/gcc/gcc/arm-wrs-vxworks/gcc'
> make[2]: *** [libgcc/./tinfo.o] Error 2
> make[2]: Leaving directory `/users/sean/gcc/gcc/arm-wrs-vxworks/gcc'
> make[1]: *** [stmp-multilib] Error 2
> make[1]: Leaving directory `/users/sean/gcc/gcc/arm-wrs-vxworks/gcc'
> make: *** [all-gcc] Error 2
>
> If you need my binutils I used please let me know.
>
> Sean
More information about the Gcc-bugs
mailing list