Re: libgcc_s not present in Yocto image

[Fred Ollinger <Fred.Ollinger@seescan.com>]

The results should tell us:

 $ files /usr/bin/testprog

What are they? (Sitting on the edge of my seat.)
________________________________________
From: Nathan Sowatskey <nathan@nathan.to>
Sent: Friday, February 5, 2016 10:09 AM
To: Fred Ollinger
Cc: Burton, Ross; yocto@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@seescan.com> wrote:
>
> My guess is that the executable is not compiled for his hardware.
>
>
> Frederick
>
> ________________________________
> From: Burton, Ross <ross.burton@intel.com>
> Sent: Friday, February 5, 2016 9:56 AM
> To: Nathan Sowatskey
> Cc: yocto@yoctoproject.org; Fred Ollinger
> Subject: Re: [yocto] libgcc_s not present in Yocto image
>
>
> On 5 February 2016 at 17:47, Nathan Sowatskey <nathan@nathan.to<mailto:nathan@nathan.to>> wrote:
> find /usr/lib -name libgcc_s.so.1
> root@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