[OE-core] meta-toolchain doesn't compile working binaries

[Björn Krombholz]

On 05/07/2014 04:58 PM, Björn Krombholz wrote:
> On 05/07/2014 02:54 PM, Björn Krombholz wrote:
>> Additional note, in case it was missed: I am using v2013.06 (yocto 1.4 
>> base, Angstrom variant)
>>
>>
>> I guess the problem is, that the relocation_sdk.py excludes /lib/ and
>> 32/64 bit variants.
> [...]
>> New and broken:
>> # ldd m4
>>          linux-vdso.so.1 (0x00007fff6c000000)
>>          libc.so.6 => 
>> /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/./../../lib/libc.so.6 
>> (0x00007fefc1de8000)
>>          /lib64/ld-linux-x86-64.so.2 (0x00007fefc2198000)
>>
>> /lib64/ obviously doesn't get replaced.
>>
>> I have no clue how to debug this any further. Not even sure if the 
>> problem is more likely related to eglibc packages or somewhere hidden 
>> in the general OE build scripts. :/
>>
>> I will build a v2013.12 version now and check if there is any difference.
> 
> Quick followup.
> 
> yocto-1.5 / Angstrom-v2013.12 _does_ work as expected.
> 

...meaning, binaries do run without segfaulting, though as Mark 
suggested, there shouldn't be any reference to the hosts /lib64/...

The ldd output for an installed nativesdk-m4 from yocto-1.5 looks like:

# ldd m4
        linux-vdso.so.1 (0x00007fff92700000)
        libc.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/./../../lib/libc.so.6 (0x00007f8aa86e8000)
        /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007f8aa8a98000)

# ls -l /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/lib/ld*
-rwxr-xr-x 1 root root 149304 May  7 16:00 /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/lib/ld-2.18-2013.10.so
lrwxrwxrwx 1 root root     18 May  7 16:01 /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/lib/ld-linux-x86-64.so.2 -> ld-2.18-2013.10.so


:-/


-- 
Björn Krombholz
pironex GmbH -- http://www.pironex.de