cross-compilation fails
Elliot Lee
sopwith@redhat.com
Fri Jun 12 08:50:00 GMT 1998
I built a cross-compiling environment (I verified that it compiles & links
a very basic program properly) and then configured libc as such:
AR=ppc-linux-ar RANLIB=ppc-linux-ranlib CC=ppc-linux-gcc ../configure \
--target=ppc-linux --enable-add-ons=crypt,linuxthreads \
--with-headers=/opt/src/sopwith/ppc/ppc-linux/sys-include \
--host=i686-unknown-linux
Unfortunately the configure script still picked up the x86 sysdeps.
(I also tried specifying AR/RANLIB/CC in configparms but those weren't
picked up at all, contrary to what INSTALL says).
I know a long time ago I did something along the lines of
../configure ppc-linux
and it built everything, but I've since been told that that will screw up
a lot of things WRT cross-compilation.
Ideas, anyone?
-- Elliot
When I die, I want to die peacefully in my sleep like my grandfather...
...not yelling and screaming like the people in the back of the
plane he was flying.
More information about the Libc-hacker
mailing list