| 1 |
Mike Frysinger wrote: |
| 2 |
|
| 3 |
> you didnt set CBUILD |
| 4 |
> |
| 5 |
>-mike |
| 6 |
> |
| 7 |
> |
| 8 |
> |
| 9 |
OK. Now my command looks like this: |
| 10 |
CFLAGS="-mcpu=arm920t -O2" CTARGET="arm-unknown-linux-gnu" |
| 11 |
CBUILD="arm-unknown-linux-gnu" ROOT=/opt/arm-gentoo-uclibc-linux/stage3/ |
| 12 |
CHOST="arm-unknown-linux-gnu" emerge -av bash |
| 13 |
|
| 14 |
After running it I get: |
| 15 |
configure:2448: checking whether the C compiler works |
| 16 |
configure:2454: ./a.out |
| 17 |
./configure: line 2455: ./a.out: cannot execute binary file |
| 18 |
configure:2457: $? = 126 |
| 19 |
configure:2466: error: cannot run C compiled programs. |
| 20 |
If you meant to cross compile, use `--host'. |
| 21 |
|
| 22 |
I get some progress when running: |
| 23 |
CFLAGS="-mcpu=arm920t -O2" CTARGET="arm-unknown-linux-gnu" |
| 24 |
CBUILD="*--host=*arm-unknown-linux-gnu" |
| 25 |
ROOT=/opt/arm-gentoo-uclibc-linux/stage3/ CHOST="arm-unknown-linux-gnu" |
| 26 |
emerge -av bash |
| 27 |
|
| 28 |
Which is kinda silly, since it is the CHOST variable, which should set |
| 29 |
the --host=${CHOST} flag for ebuild scripts. |
| 30 |
|
| 31 |
Can you help me by writing an example of how should I run the emerge |
| 32 |
command to compile for ARM? I would really appreciate that. |
| 33 |
|
| 34 |
Best wishes, |
| 35 |
Stanislaw |
| 36 |
-- |
| 37 |
gentoo-embedded@g.o mailing list |
Archives