Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
	openembedded-core@lists.openembedded.org
Subject: Re: libgcc_s.so not stripped
Date: Sun, 03 Mar 2013 17:08:34 +0000	[thread overview]
Message-ID: <1362330514.4325.30.camel@ted> (raw)
In-Reply-To: <CAMKF1sp7G1S-B5N-HR-2P_PEhkmeJnjDtskRe6EcubxiHah=nQ@mail.gmail.com>

On Wed, 2012-08-22 at 13:25 -0700, Khem Raj wrote:
> On Wed, Aug 22, 2012 at 1:15 PM, Enrico Scholz
> <enrico.scholz@sigma-chemnitz.de> wrote:
> >
> > I just noticed that libgcc_s.so.1 is not stripped in the .ipk.  Is
> > there any reason to keep the debug symbols?  Uncompressed, this makes a
> > difference of more than 1 MB.
> 
> I dont see a reason to have debug info there. Symbol table probably
> should be left in.

I noticed this when clearing out old emails and I've just posted a patch
for it.

Worryingly, there are other non-executables in the lib directories which
aren't getting stripped. I've opened a bug:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=3973

Cheers,

Richard




  parent reply	other threads:[~2013-03-03 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 20:15 libgcc_s.so not stripped Enrico Scholz
2012-08-22 20:25 ` Khem Raj
2013-03-03 17:04   ` [PATCH] libgcc: Mark libgcc_s as executable to ensure its stripped Richard Purdie
2013-03-04 20:06     ` Khem Raj
2013-03-05 13:33       ` Richard Purdie
2013-03-03 17:08   ` Richard Purdie [this message]
2013-03-04 20:03     ` libgcc_s.so not stripped Khem Raj

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=1362330514.4325.30.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox