From: Fred Ollinger <Fred.Ollinger@seescan.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Nathan Sowatskey <nathan@nathan.to>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: libgcc_s not present in Yocto image
Date: Fri, 5 Feb 2016 18:06:13 +0000 [thread overview]
Message-ID: <1454695459773.33828@seescan.com> (raw)
In-Reply-To: <CAJTo0LZFMT=JyABkd1mzLJhB9npzkTLO_sXsReMD=hKvDsuFBw@mail.gmail.com>
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
next prev parent reply other threads:[~2016-02-05 18:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 11:40 libgcc_s not present in Yocto image Nathan Sowatskey
2016-02-05 11:51 ` Tanu Kaskinen
2016-02-05 11:59 ` Burton, Ross
2016-02-05 15:24 ` Nathan Sowatskey
2016-02-05 15:50 ` Burton, Ross
2016-02-05 16:52 ` Richard Purdie
2016-02-05 17:47 ` Nathan Sowatskey
2016-02-05 17:56 ` Burton, Ross
2016-02-05 18:06 ` Fred Ollinger [this message]
2016-02-05 18:09 ` Nathan Sowatskey
2016-02-05 18:10 ` Fred Ollinger
2016-02-05 18:12 ` Nathan Sowatskey
2016-02-05 18:18 ` Fred Ollinger
2016-02-05 18:22 ` Nathan Sowatskey
2016-02-05 18:21 ` Khem Raj
2016-02-05 18:23 ` Nathan Sowatskey
2016-02-05 18:26 ` Khem Raj
2016-02-05 19:00 ` Nathan Sowatskey
2016-02-05 19:53 ` Burton, Ross
2016-02-05 19:56 ` Khem Raj
2016-02-05 20:46 ` Burton, Ross
2016-02-05 20:49 ` Khem Raj
2016-02-06 6:43 ` Nathan Sowatskey
2016-02-06 7:36 ` Nathan Sowatskey
2016-02-06 7:51 ` Khem Raj
2016-02-06 17:07 ` Nathan Sowatskey
2016-02-06 17:42 ` Khem Raj
2016-02-05 18:00 ` Fred Ollinger
2016-02-05 18:06 ` Nathan Sowatskey
2016-02-05 15:29 ` Nathan Sowatskey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1454695459773.33828@seescan.com \
--to=fred.ollinger@seescan.com \
--cc=nathan@nathan.to \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.