On Fri, 2005-06-24 at 17:19 -0700, Brian Koropoff wrote: > I've been working on building a big-endian arm (XScale) system using > crossdev to generate cross-compilers and portage to compile packages and > install them into an alternate ROOT. I have a simple > uclibc/busybox/baselayout-lite rootfs plus 2.6 kernel that boots > sucessfully. I'm now working on a full-blown glibc/baselayout rootfs > (it's a pretty beefy XScale board), but I'm having difficulty
I cross compiled from an x86 box a native armeb gcc compiler using buildroot. Unfortunately the armeb I had my hands on for a while did not have the kahunas to rebuild gcc due to limited swap space and the total size of gcc unpacked and compiled. Anyway I saved my work from before and it may be of some aid to you if you wish to continue using uClibc. http://oc12.net/~solar/uclibc/gentoo_seed_20041203_armeb-unknown-linux-uclibc.tbz2 > I'm actually using a small build script to set up environment variables > and automate a few other odds and ends, but I get the same error message > when I initiate the build manually with: > > USE="-* arm" ACCEPT_KEYWORDS=arm CBUILD=i686-pc-linux-gnu > CHOST=armeb-unknown-linux-gnu CTARGET=armeb-unknown-linux-gnu > ROOT=/image/armeb-unknown-linux-gnu-devimage emerge sys-devel/gcc > > From the looks of it, it's succesfully cross-compiling libiberty for > arm. I'm guessing what's going on is that genmodes is used in the gcc > build process and must be compiled for the build system (x86), but no > x86 libiberty is available because the configure script is not setting > this up properly. I'm not particularly familiar with the gcc build > system. What do I need to do to get a native arm compiler? Has anyone > else tried cross-compiling a native compiler toolchain for arm? The arm > stage tarballs must include a compiler, so I'm guessing it's possible to > create it with portage but I'm doing something wrong. Thanks in advance. > > -- Brian Koropoff -- Ned Ludd <[EMAIL PROTECTED]> -- [email protected] mailing list
