1 |
Hi Mike, |
2 |
|
3 |
Thanks for looking into this. |
4 |
I hadn't much time to investigate this recently but found the issue today. |
5 |
|
6 |
The problem was that a symlink for /usr was created which caused |
7 |
some trouble. After moving this to a separate partition and mounting |
8 |
during boot |
9 |
crossdev works again (among other things). |
10 |
|
11 |
Currently the latest versions of gcc,binutils,glibc and kernel are used. |
12 |
These are the same ones on the host system. |
13 |
|
14 |
Thomas |
15 |
|
16 |
On 10/14/11 01:14, Mike Frysinger wrote: |
17 |
> On Saturday 10 September 2011 12:01:10 Thomas Drueke wrote: |
18 |
>> I haven't found a log showing the outcome of the compilation making the |
19 |
>> available information |
20 |
>> restricted somehow. |
21 |
> it's farily simple code. if your gcc can't build this: |
22 |
> int foo(int *i) { |
23 |
> static __thread int j = 0; |
24 |
> return *i ? j : *i; |
25 |
> } |
26 |
> |
27 |
> it is broken |
28 |
> |
29 |
>> then stated the versions of the host system on the command line: |
30 |
>> |
31 |
>> crossdev -t armv7a-softfloat-linux-gnueabi --g 4.4.5 --l 2.12.2 --k |
32 |
>> 2.6.39 --b 2.21.1 |
33 |
> what version of gcc was actually used ? the versions you give to crossdev |
34 |
> merely say "these are the latest i want to use". if they aren't available, |
35 |
> portage will use whatever is available which is often times older than |
36 |
> requested. |
37 |
> -mike |