From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aurelien Jarno Subject: Re: hppa nptl switch Date: Wed, 02 Sep 2009 17:28:22 +0200 Message-ID: <4A9E8F16.2040302@aurel32.net> References: <119aab440909010655j148ad3b8oae5328d646ef570c@mail.gmail.com> <4A9D42C3.70103@aurel32.net> <200909012003.49114.vapier@gentoo.org> <119aab440909020709m72645cf7j61103d577bd387d7@mail.gmail.com> <20090902145548.GB10024@hall.aurel32.net> <119aab440909020824n65daaa9i1cffc3ffd5e30076@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: Mike Frysinger , debian-hppa@lists.debian.org, debian-glibc@lists.debian.org, linux-parisc To: Carlos O'Donell Return-path: In-Reply-To: <119aab440909020824n65daaa9i1cffc3ffd5e30076@mail.gmail.com> List-ID: List-Id: linux-parisc.vger.kernel.org Carlos O'Donell a =E9crit : > On Wed, Sep 2, 2009 at 10:55 AM, Aurelien Jarno= 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 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