| 1 |
On Mon, Jan 3, 2011 at 11:11 PM, Christoph Spielmann <spielc@×××××.com>wrote: |
| 2 |
|
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> Am 03.01.2011 16:33, schrieb Kfir Lavi: |
| 6 |
> |
| 7 |
> |
| 8 |
> |
| 9 |
> On Mon, Jan 3, 2011 at 2:17 PM, Christoph Spielmann <spielc@×××××.com>wrote: |
| 10 |
> |
| 11 |
>> Hi, |
| 12 |
>> |
| 13 |
>> Am 03.01.2011 10:21, schrieb Kfir Lavi: |
| 14 |
>> |
| 15 |
>> |
| 16 |
>> |
| 17 |
>> On Sun, Jan 2, 2011 at 9:31 PM, Mike Frysinger <vapier@g.o> wrote: |
| 18 |
>> |
| 19 |
>>> On Sunday, January 02, 2011 13:59:43 Peter Stuge wrote: |
| 20 |
>>> > Kfir Lavi wrote: |
| 21 |
>>> > > crossdev i686-gentoo.edge-linux-gnu |
| 22 |
>>> > |
| 23 |
>>> > .. |
| 24 |
>>> > |
| 25 |
>>> > > CBUILD=i686-pc-linux-gnu |
| 26 |
>>> > |
| 27 |
>>> > I'm pretty sure you should use i686-pc-linux-gnu as the crossdev |
| 28 |
>>> > tuple then. I don't think making up arbitrary tuples works. |
| 29 |
>>> (gentoo.edge) |
| 30 |
>>> |
| 31 |
>>> the vendor field is supposed to be arbitrary and the only char that |
| 32 |
>>> should |
| 33 |
>>> cause a split is a "-". not that we test every char though, so there |
| 34 |
>>> might be |
| 35 |
>>> bugs sitting around that most people dont notice. |
| 36 |
>>> -mike |
| 37 |
>>> |
| 38 |
>> I tried it again running |
| 39 |
>> crossdev i686-gentoo-linux-gnu |
| 40 |
>> |
| 41 |
>> |
| 42 |
>> Once again, wrong vendor field: It really should be i686-pc-linux-gnu as |
| 43 |
>> Mike suggested |
| 44 |
>> |
| 45 |
>> |
| 46 |
>> and got the same results. |
| 47 |
>> |
| 48 |
>> What can be wrong with my setup? |
| 49 |
>> |
| 50 |
>> Thanks, |
| 51 |
>> Kfir |
| 52 |
>> |
| 53 |
>> |
| 54 |
>> What I did is funny: |
| 55 |
> CBUILD=i686-pc-linux-gnu |
| 56 |
> HOSTCC=i686-pc-linux-gnu-gcc |
| 57 |
> |
| 58 |
> So it seems I'm using my native compiler?! |
| 59 |
> And I'm not using my i686-gentoo-linux-gnu-gcc |
| 60 |
> |
| 61 |
> Well in terms of crossdev i686-gentoo-linux-gnu-gcc is not a valid target |
| 62 |
> (just look at the output of crossdev --help). If you want to build x86-code |
| 63 |
> on a machine using a x86-compiler why would you want to use a |
| 64 |
> cross-compilation-environment anyway? The idea of using cross-compilation is |
| 65 |
> to build stuff for another target than the target of the host-compiler... |
| 66 |
> E.g. build arm-code on a x86-machine or compile stuff for ppc on a |
| 67 |
> x86-64-machine. |
| 68 |
> |
| 69 |
|
| 70 |
You are right, but what I'm aming for is a very easy deviation from Intel to |
| 71 |
Arm or other platform. |
| 72 |
I had my problems that where solved when cross compiling, so those problems |
| 73 |
are solved for another cross platform compilation. |
| 74 |
For example, ACE would not compile crossed, so fixing this problem with an |
| 75 |
ebuild, I'm now prepared for changing platform. |
| 76 |
I also learning how to use crossdev. As you see, it is a bit problematic for |
| 77 |
me. |
| 78 |
|
| 79 |
Kfir |
| 80 |
|
| 81 |
> |
| 82 |
> Can I see which compiler is really working if I change CBUILD to |
| 83 |
> i686-gentoo-linux-gnu? |
| 84 |
> |
| 85 |
> Thanks, |
| 86 |
> Kfir |
| 87 |
> |
| 88 |
> |
| 89 |
> |
Archives