Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] glibc and mysql 4.1.7

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Arwed von Merkatz <v.merkatz AT gmx.net>
  • To: Source Mage - Discuss <sm-discuss AT lists.ibiblio.org>
  • Subject: Re: [SM-Discuss] glibc and mysql 4.1.7
  • Date: Thu, 4 Nov 2004 06:55:35 +0100

On Wed, Nov 03, 2004 at 02:25:38PM -0800, Seth Alan Woolley wrote:
> On Wed, Nov 03, 2004 at 11:18:58PM +0100, Arwed von Merkatz wrote:
> >
> > In my opinion the best solution to this is to reverse your change to the
> > mysql spell and patch glibc to contain the string NPTL in that output.
> > I'm just glad we didn't integrate that glibc into test yet, it'll break
> > every spell that has to detect NPTL.
> > The other solution would be to grep for the new string instead, fixing
> > it in all spells. Though that would mean we would have to grep for both
> > strings, as people don't necessarily have the latest glibc snapshot
> > installed.
> > Opinions, Suggestions?
>
> We need to do both. My reason is that other packages that we aren't
> actively maintaining may expect the new output string. Patch glibc for
> now, make a routine to detect nptl as a proper grimoire function, and
> have the spells use that (so we can easily change the detection logic in
> the future).

Ok, added a grimoire function glibc_is_nptl that checks for both
strings. All spells checking for glibc should be fixed in devel and
integrated to test (the function is already in the test grimoire).
Just use
if glibc_is_nptl; then
instead of the old check.

--
Arwed v. Merkatz Source Mage GNU/Linux developer
http://www.sourcemage.org




Archive powered by MHonArc 2.6.24.

Top of Page