From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: unlvsur unlvsur <unlvsur@live.com>, Libc-help <libc-help@sourceware.org>
Subject: Re: Why glibc does not support make install-strip?
Date: Mon, 17 Jan 2022 09:03:28 -0300 [thread overview]
Message-ID: <977d1671-62be-e64e-c0c3-21356b4375fd@linaro.org> (raw)
In-Reply-To: <DM6PR05MB4697B2D51515697A0D727EECD6569@DM6PR05MB4697.namprd05.prod.outlook.com>
On 16/01/2022 18:45, unlvsur unlvsur via Libc-help wrote:
> I wonder why
I think because most consumers have specific installation procedures (such
as by splitting the debug info in different files) which makes the
install-strip not really necessary.
prev parent reply other threads:[~2022-01-17 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 21:45 unlvsur unlvsur
2022-01-17 12:03 ` Adhemerval Zanella [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=977d1671-62be-e64e-c0c3-21356b4375fd@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-help@sourceware.org \
--cc=unlvsur@live.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).