Hello David L, 2010/1/5 David L <idht4n@xxxxxxxxx>: > I need to add fortran support to a cross compiler that my company > uses. We got the compiler from codesourcery but it lacks fortran > support, so I'm trying to build one from scratch. First I'm just trying > to replicate the functionality that we currently have (C/C++) cross > compiler from i686-linux to powerpc-linux. But I can't get that > to compile. I get this error: [...] > /tmp/gccbuild/gcc-4.4.2/configure --build=i686-redhat-linux \ > --host=i686-redhat-linux \ > --target=powerpc-linux-gnu \ > --enable-threads \ > --disable-libmudflap \ > --disable-libssp \ > --disable-libstdcxx-pch \ > --with-long-double-128 \ > --with-cpu=603e \ > --enable-secureplt \ > --with-gnu-as --with-gnu-ld \ > --enable-languages=c,c++ \ > --enable-shared --enable-symvers=gnu --enable-__cxa_atexit > --disable-nls --prefix=/tmp/mygcc --enable-libgomp > --enable-poison-system-directories > --with-build-time-tools=/tmp/mybinutils/powerpc-linux-gnu/bin/ Building a cross compiler implies to build a compiler without C library headers (commonly linking to newlib), then C library and recompile. This is a very short comment, you can find better documentation under eglibc tree, http://www.eglibc.org/cgi-bin/viewcvs.cgi/branches/eglibc-2_5/libc/EGLIBC.cross-building?rev=2038&view=markup Are not you supposed to use --with-headers/--with-libs (deprecated) or --sysroot to build a cross thingy? Best luck! -- Héctor Orón "Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us."
