1 |
On 2010-09-29, meino.cramer@×××.de <meino.cramer@×××.de> wrote: |
2 |
|
3 |
>> > (And in this context: The audio application "chuck" is only as 32bit |
4 |
>> > application available currently. How is it possible to compile this |
5 |
>> > on a 64bit system?) |
6 |
>> |
7 |
>> You use a compiler that generates code for a the desired 32-bit |
8 |
>> architecture. The "width" of the host is immaterial. |
9 |
|
10 |
> Thank you very much for your offered help! |
11 |
> |
12 |
> Sorry, sorry I think my English confused a lot of infos... |
13 |
|
14 |
Cross-building stuff is just plain confusing. |
15 |
|
16 |
> I'll try it again. |
17 |
> |
18 |
> Setup BEFORE I switched to 64bit Gentoo Linux. |
19 |
> * a "normal" system gcc as installed by emerge usually on many (all?) gentoo |
20 |
> systems... |
21 |
> * a "crosscompiling" gcc in source form. Compiled with the "normal" |
22 |
> gcc to an executable which runs on the 32bit Gentoo system and |
23 |
> produces executables/kernel to run on the ATMEL AT91RM9200 (yes, |
24 |
> you're right - this typo was mine ;) ). |
25 |
> * Additional "chuck" audio application only available for 32bit |
26 |
> Linux, also compiled with the "normal" gcc |
27 |
> |
28 |
> Wanted setup on my shiny new 64bit Gentoo Linux: |
29 |
> * a "normal" system gcc as installed by emerge usually on many (all?) gentoo |
30 |
> systems... (==> already there and living quite well) |
31 |
> * a "crosscompiling" gcc in source form. To be Compiled with the "normal" |
32 |
> gcc to an executable which runs on the 64bit Gentoo system and |
33 |
> produces executables/kernel to run on the ATMEL AT91RM9200 (yes, |
34 |
> you're right - this typo was mine ;) ) . |
35 |
|
36 |
All you need to do is build a cross compiler for the ARM9 target the |
37 |
same way you did before. The width of the host where you're building |
38 |
things doesn't matter (if it does, that's a bug in gcc or binutils). |
39 |
|
40 |
I've had excellent results using the crosstool-ng makefile: |
41 |
|
42 |
http://ymorin.is-a-geek.org/projects/crosstool |
43 |
|
44 |
Crosstool is used by a lot of embedded developers. If there were |
45 |
problems building an ARM comiler on an AMD64 host, Yann Morin et al. |
46 |
are your best bet for a solution. You may want to take a look at the |
47 |
crossgcc mailing list: |
48 |
|
49 |
http://news.gmane.org/gmane.comp.gcc.cross-compiling |
50 |
http://sourceware.org/ml/crossgcc/ |
51 |
|
52 |
From a brief search of the mailing list, it appears that building an |
53 |
ARM compiler on an AMD64 machines works just fine. |
54 |
|
55 |
or, |
56 |
|
57 |
It's quite likely that you can install IA32 libraries on your AMD64 |
58 |
host OS and then use the exact same compiler executable you used |
59 |
before. |
60 |
|
61 |
> OR: compiled to be an 32bit gcc-executable which generate |
62 |
> executable binaries for my ATMEL cookie. As long a 64bit-executable |
63 |
> of gcc can do the job I would prefer that solution of course. |
64 |
|
65 |
You really don't want to do that. It's rather tricky, and it |
66 |
shouldn't be required. |
67 |
|
68 |
> * Additional "chuck" audio application only available for 32bit |
69 |
> Linux, to be compiled with the "normal" gcc to be a 32 bit |
70 |
> executable since not 64bit-ready. |
71 |
|
72 |
Just use the arm-linux-gcc compiler and you should be fine regardless |
73 |
of the width of the host on which you built the arm-linux-gcc |
74 |
compiler. |
75 |
|
76 |
-- |
77 |
Grant Edwards grant.b.edwards Yow! It's the RINSE CYCLE!! |
78 |
at They've ALL IGNORED the |
79 |
gmail.com RINSE CYCLE!! |