| 1 |
On Fri, 2005-06-24 at 17:19 -0700, Brian Koropoff wrote: |
| 2 |
> I've been working on building a big-endian arm (XScale) system using |
| 3 |
> crossdev to generate cross-compilers and portage to compile packages and |
| 4 |
> install them into an alternate ROOT. I have a simple |
| 5 |
> uclibc/busybox/baselayout-lite rootfs plus 2.6 kernel that boots |
| 6 |
> sucessfully. I'm now working on a full-blown glibc/baselayout rootfs |
| 7 |
> (it's a pretty beefy XScale board), but I'm having difficulty |
| 8 |
|
| 9 |
|
| 10 |
|
| 11 |
I cross compiled from an x86 box a native armeb gcc compiler using |
| 12 |
buildroot. Unfortunately the armeb I had my hands on for a while did not |
| 13 |
have the kahunas to rebuild gcc due to limited swap space and the total |
| 14 |
size of gcc unpacked and compiled. |
| 15 |
|
| 16 |
Anyway I saved my work from before and it may be of some aid to you if |
| 17 |
you wish to continue using uClibc. |
| 18 |
http://oc12.net/~solar/uclibc/gentoo_seed_20041203_armeb-unknown-linux-uclibc.tbz2 |
| 19 |
|
| 20 |
|
| 21 |
> I'm actually using a small build script to set up environment variables |
| 22 |
> and automate a few other odds and ends, but I get the same error message |
| 23 |
> when I initiate the build manually with: |
| 24 |
> |
| 25 |
> USE="-* arm" ACCEPT_KEYWORDS=arm CBUILD=i686-pc-linux-gnu |
| 26 |
> CHOST=armeb-unknown-linux-gnu CTARGET=armeb-unknown-linux-gnu |
| 27 |
> ROOT=/image/armeb-unknown-linux-gnu-devimage emerge sys-devel/gcc |
| 28 |
> |
| 29 |
> From the looks of it, it's succesfully cross-compiling libiberty for |
| 30 |
> arm. I'm guessing what's going on is that genmodes is used in the gcc |
| 31 |
> build process and must be compiled for the build system (x86), but no |
| 32 |
> x86 libiberty is available because the configure script is not setting |
| 33 |
> this up properly. I'm not particularly familiar with the gcc build |
| 34 |
> system. What do I need to do to get a native arm compiler? Has anyone |
| 35 |
> else tried cross-compiling a native compiler toolchain for arm? The arm |
| 36 |
> stage tarballs must include a compiler, so I'm guessing it's possible to |
| 37 |
> create it with portage but I'm doing something wrong. Thanks in advance. |
| 38 |
> |
| 39 |
> -- Brian Koropoff |
| 40 |
-- |
| 41 |
Ned Ludd <solar@g.o> |
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-embedded@g.o mailing list |
Archives