[yocto] libgcc_s not present in Yocto image

[Fred Ollinger]

What's the result of:

 $ cat /proc/cpuinfo

(So far, it seems like my hunch was wrong.)

Frederick
________________________________________
From: Nathan Sowatskey <nathan at nathan.to>
Sent: Friday, February 5, 2016 10:12 AM
To: Fred Ollinger
Cc: Burton, Ross; yocto at yoctoproject.org
Subject: Re: [yocto] libgcc_s not present in Yocto image

file /usr/bin/testprog
/usr/bin/testprog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=26317096ed83d21bc6808f0d2d47b12de1ab31ce, not stripped

Thoughts?

> On 5 Feb 2016, at 19:10, Fred Ollinger <Fred.Ollinger at seescan.com> wrote:
>
> The results should tell us:
>
> $ files /usr/bin/testprog
>
> What are they? (Sitting on the edge of my seat.)
> ________________________________________
> From: Nathan Sowatskey <nathan at nathan.to>
> Sent: Friday, February 5, 2016 10:09 AM
> To: Fred Ollinger
> Cc: Burton, Ross; yocto at yoctoproject.org
> Subject: Re: [yocto] libgcc_s not present in Yocto image
>
> Thanks Fred.
>
> I am using qemux86_64 on Intel i7 chips with OSX.  The target is likewise Intel.
>
> I am assuming that is quite generic, but …
>
> Regards
>
> Nathan
>
>> On 5 Feb 2016, at 19:06, Fred Ollinger <Fred.Ollinger at seescan.com> wrote:
>>
>> My guess is that the executable is not compiled for his hardware.
>>
>>
>> Frederick
>>
>> ________________________________
>> From: Burton, Ross <ross.burton at intel.com>
>> Sent: Friday, February 5, 2016 9:56 AM
>> To: Nathan Sowatskey
>> Cc: yocto at yoctoproject.org; Fred Ollinger
>> Subject: Re: [yocto] libgcc_s not present in Yocto image
>>
>>
>> On 5 February 2016 at 17:47, Nathan Sowatskey <nathan at nathan.to<mailto:nathan at nathan.to>> wrote:
>> find /usr/lib -name libgcc_s.so.1
>> root at qemux86-64:~#
>>
>> I don't have that lib.
>>
>> As I said, libgcc_s.so.1 is in /lib, not /usr/lib.
>>
>> With ldd I get:
>>
>> ldd /usr/bin/testprog
>> /usr/bin/ldd: line 117: /usr/bin/testprog: No such file or directory
>>
>> Well ldd appears to be having a bit of a panic.  Try objdump -p /usr/bin/testprog instead.
>>
>> Ross
>