From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] Makefile: respect strip exclusions for special libraries
Date: Mon, 4 Feb 2019 21:06:27 +0100 [thread overview]
Message-ID: <20190204210627.4fe621fc@windsurf> (raw)
In-Reply-To: <CANQCQpYFv3Gt_dkg_T_7ppb1Fiy8JmXsHX6pDrGvJzZrZOvRhg@mail.gmail.com>
On Mon, 4 Feb 2019 12:58:08 -0600
Matthew Weber <matthew.weber@collins.com> wrote:
> > +# Special stripping (only debugging symbols) for libpthread and ld-*.so.
> > +STRIP_FIND_SPECIAL_LIBS_CMD = \
> > + $(STRIP_FIND_COMMON_CMD) \
> > + \( -name 'ld-*.so*' -o -name 'libpthread*.so*' \) \
>
> The answer to you question about needing to strip libpthread for only
> glibc is true. I did poke around a bit and checked if libthread_db
> needed symbols and verified it can be stripped. Do you think a noted
> should be added to state the libpthread stripping detail?
So basically thread debugging on musl/uclibc works even if libc.so is
stripped ?
In any case, thanks for you investigation on this. I'm not sure adding
a note here is really useful: uclibc/musl simply don't have any
libpthread, and it's OK to not do anything special for uclibc/musl here.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-04 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 15:56 [Buildroot] [git commit] Makefile: respect strip exclusions for special libraries Thomas Petazzoni
2019-02-04 18:58 ` Matthew Weber
2019-02-04 20:06 ` Thomas Petazzoni [this message]
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=20190204210627.4fe621fc@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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