From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Subject: Re: glibc updated
Date: Tue, 18 Jul 2017 17:13:20 +0200 [thread overview]
Message-ID: <7d699079b866802cfcbe1a98c1dea56d@sf-tec.de> (raw)
In-Reply-To: <23667583-845e-3ce9-f327-456fd042cc32@bell.net>
Am 2017-07-18 16:32, schrieb John David Anglin:
> On 2017-07-17 12:33 PM, John David Anglin wrote:
>> I would like to know if the gentoo folks would consider fixing the
>> __gmon_start__ bug:
>> https://sourceware.org/bugzilla/show_bug.cgi?id=19170
>>
>> There is some risk in applying the patch as rebuilding a library
>> package may break other
>> packages which depend on the library. This could break critical tools
>> such as binutils and
>> gcc. In which case, some manual intervention may be needed. However,
>> the transition
>> on Debian went fairly smoothly. As a result, we no longer have the
>> external symbol
>> __gmon_start exposed and we have correct library dependencies.
>>
>> The issues with _init referred to in the BZ report are fixed. It is
>> now PIC; and PIE applications
>> work on hppa thanks to Alan Modra.
> Helge: we need to add PIE load address to the kernel TODO list if it's
> not already there.
>>
>> Although not ideal, we could keep the __gmon_start__ patch in Debian.
>>
> The other approach is to install the __gmon_start__ patch and let
> gentoo revert it. I'm starting
> to think this is best.
I don't think there will be a big problem for Gentoo to accept it, as
long as there is a working upgrade path like "build glibc with flag
-special-foo, rebuild system, remove flag and rebuild glibc again". And
of course a hint in the release notes so it will be obvious to the
packagers what they have to take care of. That flag thing is something
that Gentoo probably can add to their build scripts, something that e.g.
keeps the symbol in the lib without exporting it during linking, so it
would be resolvable first and the reference goes away on rebuild. Or
whatever ;)
Eike
next prev parent reply other threads:[~2017-07-18 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 11:54 glibc updated John David Anglin
2017-07-17 16:00 ` Carlos O'Donell
2017-07-17 16:33 ` John David Anglin
2017-07-18 14:32 ` John David Anglin
2017-07-18 15:13 ` Rolf Eike Beer [this message]
2017-07-18 16:30 ` John David Anglin
2017-07-18 19:39 ` Rolf Eike Beer
2017-07-18 20:26 ` John David Anglin
2017-07-19 15:06 ` John David Anglin
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=7d699079b866802cfcbe1a98c1dea56d@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.kernel.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