1 |
Oh, okay, that worked. But I'm not shure if the created code is realy |
2 |
for use with i386 CPUs. I compiled syslinux and GRUB and nothing seems |
3 |
to work on the used system (e.g. GRUB only shows up his name at power on |
4 |
and nothing more happens). |
5 |
|
6 |
Lutz |
7 |
|
8 |
Kevin F. Quinn (Gentoo) wrote: |
9 |
> On Mon, 06 Mar 2006 10:35:10 +0100 |
10 |
> Lutz Schönemann <lutz.schoenemann@××××××××××××××.de> wrote: |
11 |
> |
12 |
> |
13 |
>>Hi, |
14 |
>>I've problems building an working Cross-Compiler to use it for an |
15 |
>>i386 embedded system. Until now I've tried the following two things: |
16 |
>> |
17 |
>>- Using crossdev: |
18 |
>>The crossdev script worked fine and installed the whole toolchain |
19 |
>>(stage4: binutils, gcc, linux-headers, etc.). The trouble is that |
20 |
>>when I want to merge a packege with this compiler (e.g.: |
21 |
>>CFLAGS="-arch=i386" ROOT=/tmp/cross/ CHOST=i386-unknown-linux-gnu |
22 |
>>emerge sys-boot/syslinux) it ends up with the message that the |
23 |
>>compiler is unable to build executables. |
24 |
> |
25 |
> |
26 |
> Just in case that wasn't a typo in transcription - you need |
27 |
> CFLAGS="-march=i386" (with an 'm'). You should look at the config.log |
28 |
> etc to find out exactly why the compiler couldn't build executables. |
29 |
> |
30 |
> BTW again just in case - if your host is an x86 system, you don't need a |
31 |
> cross-compiler as your host compiler can build for all x86 variants - |
32 |
> it's enough to get the CFLAGS right; e.g. |
33 |
> |
34 |
> CFLAGS="-march=i386" ROOT=/tmp/cross emerge <pkg> |
35 |
> |
36 |
|
37 |
|
38 |
-- |
39 |
Lutz Schönemann |
40 |
|
41 |
Addr: Fraunhofer Institut für Sichere Informations Technologie SIT |
42 |
Rheinstrasse 75, 64295 Darmstadt, Germany |
43 |
WWW: http://www.sit.fraunhofer.de |
44 |
|
45 |
Zertifizierungen in der FhG: http://pki.fraunhofer.de |
46 |
-- |
47 |
gentoo-embedded@g.o mailing list |