From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: libgcc_s.so not stripped
Date: Wed, 22 Aug 2012 22:15:11 +0200 [thread overview]
Message-ID: <ly628a8z00.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
Hi,
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.
Enrico
next reply other threads:[~2012-08-22 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 20:15 Enrico Scholz [this message]
2012-08-22 20:25 ` libgcc_s.so not stripped 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 ` libgcc_s.so not stripped Richard Purdie
2013-03-04 20:03 ` 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=ly628a8z00.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox