From: Frans Pop <elendil@planet.nl>
To: debian-hppa@lists.debian.org
Cc: debian-glibc@lists.debian.org,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: hppa nptl switch
Date: Mon, 31 Aug 2009 18:46:48 +0200 [thread overview]
Message-ID: <200908311846.49969.elendil@planet.nl> (raw)
In-Reply-To: <119aab440908310810g6fa7e3d8s71f1f4bea0041f1@mail.gmail.com>
Carlos O'Donell wrote:
>> In practice it shouldn't be problem at all.
>> Debian should make sure that binary/library compiled
>> against NPTL-hppa-glibc will require NPTL-hppa-glibc
>> by proper Depends: line like "libc6 (>= 2.10)".
>
> Does every package have to do this? I'm not very familiar with all the
> packaging requirements.
It is something that should automatically get done correctly as long as
the libc-dev package defines the minimum version that way.
The mechanism that determines this is in /var/lib/dpkg/info/libc6.shlibs.
Currently this has lines like:
libc 6 libc6 (>= 2.9)
It's virtually certain that the shlibs file will be updated to read
'(>= 2.10)' when the glibc maintainers switch to that version.
Cheers,
FJP
next prev parent reply other threads:[~2009-08-31 16:46 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 [this message]
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
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=200908311846.49969.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=debian-glibc@lists.debian.org \
--cc=debian-hppa@lists.debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.