All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
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, 05 Feb 2016 16:52:48 +0000	[thread overview]
Message-ID: <1454691168.27087.278.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LbbM_TXswmQxbqP5yr4Pf9geh7Ru6=iD3nHNHscC8q-nQ@mail.gmail.com>

On Fri, 2016-02-05 at 15:50 +0000, Burton, Ross wrote:
> 
> On 5 February 2016 at 15:24, Nathan Sowatskey <nathan@nathan.to>
> wrote:
> > I suspect that my test program, which was supplied to me as a .deb
> > package, was compiled on Ubuntu, and so links to libgcc_s.so.1. I
> > can’t see any obvious way to get libgcc_s.so.1 on Yocto. I already
> > have:
> > 
> libgcc contains /lib/libgcc_s.so.1, so it should be installed in your
> image already:
> 
> How are you determining that it isn't in your image, and that your
> application doesn't work?

Note that the build system will only install libraries that are
actually used. It nothing needs libgcc_s, it won't get installed.

There is a lot less than you'd think which actually links against it so
it is quite possible its not in your image since nothing needed it.

Cheers,

Richard


  reply	other threads:[~2016-02-05 16:53 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 [this message]
2016-02-05 17:47       ` Nathan Sowatskey
2016-02-05 17:56         ` Burton, Ross
2016-02-05 18:06           ` Fred Ollinger
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=1454691168.27087.278.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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.