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

OT:PPC->i386 cross-compiling



Hello List,

I've been working on cross-compilation i386->PPC/PPC->i386 and am facing a 
final roadblock. 

I have successfully build a gcc 3.2.2 cross-compiler for i386->ppc and am now 
attempting to build a cross for ppc->i386. All steps succeed with the 
exception of the final gcc rebuild. The tail end of the error is appended 
below, and I have the entire log as well, if anyone is interested.

In addition to gcc 3.2.2, I'm using binutils-2.13.2.1 and glibc-2.3.1 with
linuxthreads-2.3.1.  glibc-2.3.2 refuses to compile if gcc is compiled with
--disable-shared, so I dropped back a version.

I am configuring gcc with:

./configure  --host=powerpc-linux \
--build=powerpc-linux --target=i386-linux \
--prefix=/home/jeff/i386 \
--with-headers=/home/jeff/i386/include \
--with-libs=/home/jeff/i386/lib --enable-shared --disable-nls \
--enable-add-ons --enable-threads=posix --enable-languages=c,c++

Thanks for any assistance,

Jeff Elkins

==============
In file included from /home/jeff/i386/include/math.h:362,
 from /home/jeff/gcc-3.2.2/i386-linux/libstdc++-v3/include/cmath:51,
from
/home/jeff/gcc-3.2.2/i386-linux/libstdc++-v3/include/bits/locale_facets.tcc:4
1, from /home/jeff/gcc-3.2.2/i386-linux/libstdc++-v3/include/locale:46, from
 /home/jeff/gcc-3.2.2/i386-linux/libstdc++-v3/include/bits/ostream.tcc:37,
 from /home/jeff/gcc-3.2.2/i386-linux/libstdc++-v3/include/ostream:275, from
 /home/jeff/gcc-3.2.2/i386-linux/libstdc++-v3/include/bitset:58, from
 bitset.cc:43:
/home/jeff/i386/include/bits/mathinline.h: In function `double
 log1p(double)': /home/jeff/i386/include/bits/mathinline.h:539: `logl'
 undeclared (first use this function)
/home/jeff/i386/include/bits/mathinline.h:539: (Each undeclared identifier is
   reported only once for each function it appears in.)
make[3]: *** [bitset.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive-am] Error 2
make: *** [all-target-libstdc++-v3] Error 2



Reply to: