From: unlvsur unlvsur <unlvsur@live.com>
To: Bill Cunningham <bill.cu1234@gmail.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
unlvsur unlvsur via Libc-alpha <libc-alpha@sourceware.org>
Subject: RE: Why glibc does not support make install-strip?
Date: Mon, 17 Jan 2022 23:14:58 +0000 [thread overview]
Message-ID: <DM6PR05MB4697647FAE4883E01B43F441D6579@DM6PR05MB4697.namprd05.prod.outlook.com> (raw)
In-Reply-To: <68e82c38-5b85-e726-177c-cddbfffcab8e@gmail.com>
That does not make sense since gcc and libstdc++ work the same way. Same with LLVM cmake things.
You just make install -j, it won’t strip binary.
While I have to manually x86_64-ubuntu-linux-strip –strip-unneeded * on every directory which is ridiculous.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
From: Bill Cunningham<mailto:bill.cu1234@gmail.com>
Sent: Monday, January 17, 2022 15:10
To: Adhemerval Zanella<mailto:adhemerval.zanella@linaro.org>; unlvsur unlvsur<mailto:unlvsur@live.com>
Subject: Re: Why glibc does not support make install-strip?
On 1/17/2022 7:03 AM, Adhemerval Zanella via Libc-help wrote:
>
> 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.
I myself use CFLAGS='-O2' and leave out the -g for adding debugging code
and the same with CXXFLAGS. And don't mess with the 'strip' command. FWIW.
B
next parent reply other threads:[~2022-01-17 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR05MB4697B2D51515697A0D727EECD6569@DM6PR05MB4697.namprd05.prod.outlook.com>
[not found] ` <977d1671-62be-e64e-c0c3-21356b4375fd@linaro.org>
[not found] ` <68e82c38-5b85-e726-177c-cddbfffcab8e@gmail.com>
2022-01-17 23:14 ` unlvsur unlvsur [this message]
2022-01-18 3:51 ` Adhemerval Zanella
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=DM6PR05MB4697647FAE4883E01B43F441D6579@DM6PR05MB4697.namprd05.prod.outlook.com \
--to=unlvsur@live.com \
--cc=adhemerval.zanella@linaro.org \
--cc=bill.cu1234@gmail.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).