From: Aurelien Jarno <aurelien@aurel32.net>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Mike Frysinger <vapier@gentoo.org>,
debian-hppa@lists.debian.org, debian-glibc@lists.debian.org,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: hppa nptl switch
Date: Wed, 02 Sep 2009 17:28:22 +0200 [thread overview]
Message-ID: <4A9E8F16.2040302@aurel32.net> (raw)
In-Reply-To: <119aab440909020824n65daaa9i1cffc3ffd5e30076@mail.gmail.com>
Carlos O'Donell a =E9crit :
> On Wed, Sep 2, 2009 at 10:55 AM, Aurelien Jarno<aurelien@aurel32.net>=
wrote:
>> On Wed, Sep 02, 2009 at 10:09:22AM -0400, Carlos O'Donell wrote:
>>> On Tue, Sep 1, 2009 at 8:03 PM, Mike Frysinger<vapier@gentoo.org> w=
rote:
>>>> i think the question was one about packaging rather than general u=
se ? if you
>>>> build a package against a newer glibc version but it only uses old=
er symbols,
>>>> then in theory it should work fine with older glibc versions. if =
the symbol
>>>> changes between versions, then it should have corresponding symbol=
version
>>>> changes as well (which will automatically be recorded in the binar=
y).
>>> Yes, the question is specifically about packaging.
>>>
>>> If the answer is "Debian does not prevent you from downgrading glib=
c,
>>> even if you have new packages built against the new glibc", then I
>>> accept that.
>>>
>> With the correct shlibs and symbol files, all packages built against=
the
>> new glibc will depends on libc6 (>=3D 2.10). This way it won't be po=
ssible
>> to downgrade the libc6 packages is packages compiled against the new
>> glibc are installed.
>=20
> Is the shlibs sufficient? For example, data structures aren't
> versioned. In my new NPTL patches, I change PTHREAD_COND_INITIALIZER,
> but I do not version anything (not required because the current
> functions support both old and new style initializers), therefore the
> symbol files will be identical?
>=20
Yes, but we can change the symbol files so that all versions of all
symbols (for current symbols) resolve to libc6 (>=3D 2.10). This has
already been done for example for the sparc v8 to sparc v8plus ABI chan=
ge.
--=20
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-09-02 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.62.0908181940440.7856@sci.felk.cvut.cz>
[not found] ` <119aab440908181851i174315c6lebacea921046bbb0@mail.gmail.com>
[not found] ` <20090819124816.GC2517@hall.aurel32.net>
2009-08-31 5:01 ` hppa nptl switch Carlos O'Donell
2009-08-31 8:16 ` Petr Salinger
2009-08-31 15:10 ` Carlos O'Donell
2009-08-31 16:46 ` Frans Pop
2009-08-31 16:53 ` Carlos O'Donell
2009-09-01 6:08 ` Aurelien Jarno
2009-09-01 13:55 ` Carlos O'Donell
2009-09-01 14:40 ` Thibaut VARENE
2009-09-01 15:50 ` Aurelien Jarno
2009-09-02 0:03 ` Mike Frysinger
2009-09-02 14:09 ` Carlos O'Donell
2009-09-02 14:55 ` Aurelien Jarno
2009-09-02 15:24 ` Carlos O'Donell
2009-09-02 15:28 ` Aurelien Jarno [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=4A9E8F16.2040302@aurel32.net \
--to=aurelien@aurel32.net \
--cc=carlos@systemhalted.org \
--cc=debian-glibc@lists.debian.org \
--cc=debian-hppa@lists.debian.org \
--cc=linux-parisc@vger.kernel.org \
--cc=vapier@gentoo.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 NNTP newsgroup(s).