From: Florian Weimer <fweimer@redhat.com>
To: libc-stable@sourceware.org
Subject: Re: [2.28 COMMITTED] memusagestat: use local glibc when linking [BZ #18465]
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <87bm0t9stu.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20190424175839.EAE1982F876C@oldenburg2.str.redhat.com> (Florian Weimer's message of "Wed, 24 Apr 2019 19:58:39 +0200")
* Florian Weimer:
> From: Mike Frysinger <vapier@gentoo.org>
>
> The memusagestat is the only binary that has its own link line which
> causes it to be linked against the existing installed C library. It
> has been this way since it was originally committed in 1999, but I
> don't see any reason as to why. Since we want all the programs we
> build locally to be against the new copy of glibc, change the build
> to be like all other programs.
>
> (cherry picked from commit f9b645b4b0a10c43753296ce3fa40053fa44606a)
Likewise, I had to revert this because of -Wl,-rpath-link= ordering
issues.
Thanks,
Florian
prev parent reply other threads:[~2019-04-26 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Florian Weimer
2019-01-01 0:00 ` Florian Weimer [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=87bm0t9stu.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-stable@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).