From: Phil Blundell <philb@gnu.org>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: libgcc_s.so.1 not stripped
Date: Tue, 19 Jul 2011 16:57:14 +0100 [thread overview]
Message-ID: <1311091035.30326.36.camel@phil-desktop> (raw)
I noticed this morning that libgcc_s.so.1 is no longer being stripped
correctly. I'm not quite sure at what point this started happening.
From a first inspection the problem seems to be that it's losing the +x
bit in the mode which is causing package.bbclass to think it isn't an
executable that requires stripping.
p.
reply other threads:[~2011-07-19 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1311091035.30326.36.camel@phil-desktop \
--to=philb@gnu.org \
--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