| 1 |
Hi, |
| 2 |
|
| 3 |
Am 03.01.2011 16:33, schrieb Kfir Lavi: |
| 4 |
> |
| 5 |
> |
| 6 |
> On Mon, Jan 3, 2011 at 2:17 PM, Christoph Spielmann <spielc@×××××.com |
| 7 |
> <mailto:spielc@×××××.com>> wrote: |
| 8 |
> |
| 9 |
> Hi, |
| 10 |
> |
| 11 |
> Am 03.01.2011 10:21, schrieb Kfir Lavi: |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> On Sun, Jan 2, 2011 at 9:31 PM, Mike Frysinger <vapier@g.o |
| 15 |
>> <mailto:vapier@g.o>> wrote: |
| 16 |
>> |
| 17 |
>> On Sunday, January 02, 2011 13:59:43 Peter Stuge wrote: |
| 18 |
>> > Kfir Lavi wrote: |
| 19 |
>> > > crossdev i686-gentoo.edge-linux-gnu |
| 20 |
>> > |
| 21 |
>> > .. |
| 22 |
>> > |
| 23 |
>> > > CBUILD=i686-pc-linux-gnu |
| 24 |
>> > |
| 25 |
>> > I'm pretty sure you should use i686-pc-linux-gnu as the |
| 26 |
>> crossdev |
| 27 |
>> > tuple then. I don't think making up arbitrary tuples works. |
| 28 |
>> (gentoo.edge) |
| 29 |
>> |
| 30 |
>> the vendor field is supposed to be arbitrary and the only |
| 31 |
>> char that should |
| 32 |
>> cause a split is a "-". not that we test every char though, |
| 33 |
>> so there might be |
| 34 |
>> bugs sitting around that most people dont notice. |
| 35 |
>> -mike |
| 36 |
>> |
| 37 |
>> I tried it again running |
| 38 |
>> crossdev i686-gentoo-linux-gnu |
| 39 |
> |
| 40 |
> Once again, wrong vendor field: It really should be |
| 41 |
> i686-pc-linux-gnu as Mike suggested |
| 42 |
> |
| 43 |
> |
| 44 |
>> and got the same results. |
| 45 |
>> |
| 46 |
>> What can be wrong with my setup? |
| 47 |
>> |
| 48 |
>> Thanks, |
| 49 |
>> Kfir |
| 50 |
> |
| 51 |
> What I did is funny: |
| 52 |
> CBUILD=i686-pc-linux-gnu |
| 53 |
> HOSTCC=i686-pc-linux-gnu-gcc |
| 54 |
> |
| 55 |
> So it seems I'm using my native compiler?! |
| 56 |
> And I'm not using my i686-gentoo-linux-gnu-gcc |
| 57 |
Well in terms of crossdev i686-gentoo-linux-gnu-gcc is not a valid |
| 58 |
target (just look at the output of crossdev --help). If you want to |
| 59 |
build x86-code on a machine using a x86-compiler why would you want to |
| 60 |
use a cross-compilation-environment anyway? The idea of using |
| 61 |
cross-compilation is to build stuff for another target than the target |
| 62 |
of the host-compiler... E.g. build arm-code on a x86-machine or compile |
| 63 |
stuff for ppc on a x86-64-machine. |
| 64 |
> |
| 65 |
> Can I see which compiler is really working if I change CBUILD to |
| 66 |
> i686-gentoo-linux-gnu? |
| 67 |
> |
| 68 |
> Thanks, |
| 69 |
> Kfir |
Archives