| 1 |
Use crossdev |
| 2 |
|
| 3 |
--iggy |
| 4 |
|
| 5 |
Brian Koropoff wrote: |
| 6 |
> I've been working on building a big-endian arm (XScale) system using |
| 7 |
> crossdev to generate cross-compilers and portage to compile packages and |
| 8 |
> install them into an alternate ROOT. I have a simple |
| 9 |
> uclibc/busybox/baselayout-lite rootfs plus 2.6 kernel that boots |
| 10 |
> sucessfully. I'm now working on a full-blown glibc/baselayout rootfs |
| 11 |
> (it's a pretty beefy XScale board), but I'm having difficulty |
| 12 |
> cross-compiling a native gcc toolchain for arm. The gcc compile fails |
| 13 |
> with the following error: |
| 14 |
> |
| 15 |
> make[2]: *** No rule to make target |
| 16 |
> `../build-i686-pc-linux-gnu/libiberty/libiberty.a', needed by |
| 17 |
> `genmodes'. Stop. |
| 18 |
> make[2]: *** Waiting for unfinished jobs.... |
| 19 |
> make[2]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/gcc' |
| 20 |
> make[1]: *** [stage1_build] Error 2 |
| 21 |
> make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/gcc' |
| 22 |
> make: *** [bootstrap-lean] Error 2 |
| 23 |
> |
| 24 |
> I'm actually using a small build script to set up environment variables |
| 25 |
> and automate a few other odds and ends, but I get the same error message |
| 26 |
> when I initiate the build manually with: |
| 27 |
> |
| 28 |
> USE="-* arm" ACCEPT_KEYWORDS=arm CBUILD=i686-pc-linux-gnu |
| 29 |
> CHOST=armeb-unknown-linux-gnu CTARGET=armeb-unknown-linux-gnu |
| 30 |
> ROOT=/image/armeb-unknown-linux-gnu-devimage emerge sys-devel/gcc |
| 31 |
> |
| 32 |
> From the looks of it, it's succesfully cross-compiling libiberty for |
| 33 |
> arm. I'm guessing what's going on is that genmodes is used in the gcc |
| 34 |
> build process and must be compiled for the build system (x86), but no |
| 35 |
> x86 libiberty is available because the configure script is not setting |
| 36 |
> this up properly. I'm not particularly familiar with the gcc build |
| 37 |
> system. What do I need to do to get a native arm compiler? Has anyone |
| 38 |
> else tried cross-compiling a native compiler toolchain for arm? The arm |
| 39 |
> stage tarballs must include a compiler, so I'm guessing it's possible to |
| 40 |
> create it with portage but I'm doing something wrong. Thanks in advance. |
| 41 |
> |
| 42 |
> -- Brian Koropoff |
| 43 |
|
| 44 |
|
| 45 |
-- |
| 46 |
Stuff for sale -- http://www.brianandsara.net/temp/forsale.html |
| 47 |
Gentoo Linux -- http://www.gentoo.org |
| 48 |
IVTV -- http://ivtv.writeme.ch |
| 49 |
-- |
| 50 |
gentoo-embedded@g.o mailing list |
Archives