linux-mips
[Top] [All Lists]

Re: glibc-2.3.4 mips64 compilation failure

To: Daniel Jacobowitz <dan@debian.org>
Subject: Re: glibc-2.3.4 mips64 compilation failure
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Thu, 26 May 2005 20:34:28 +0100 (BST)
Cc: maxim@mox.ru, linux-mips@linux-mips.org
In-reply-to: <20050526190554.GA16765@nevyn.them.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <6097c4905052609326a4c1232@mail.gmail.com> <20050526170603.GA13272@nevyn.them.org> <Pine.LNX.4.61L.0505261815330.29423@blysk.ds.pg.gda.pl> <20050526190554.GA16765@nevyn.them.org>
Sender: linux-mips-bounce@linux-mips.org
On Thu, 26 May 2005, Daniel Jacobowitz wrote:

> >  Or too new, sigh...  See: 
> > "http://sources.redhat.com/bugzilla/show_bug.cgi?id=758";.  Unfortunately 
> > it's not clear to me what "the 2.3 branch inclusion criteria" are and it's 
> > a pity the MIPS port of glibc is unmaintained these days...
> 
> He did post the criteria.  You can find them in the list archives
> though I don't have a URL handy.

 Well, the criteria probably don't change that much if at all from one 
stable branch to another, so having them somewhere at one of the GNU libc 
web pages (probably the sourceware's is the right one for such internal 
guidelines) wouldn't hurt, like it's done e.g. with GCC.  I can't recall 
if I tried searching the mailing list previously, but now "branch 
inclusion criteria" doesn't return anything, so even your hint isn't 
especially useful (and I don't want to spend my life digging the archives, 
sorry).  I'm somewhat surprised, actually, as I'm subscribed to the 
libc-alpha list for quite some time now, certainly since before the branch 
was created and I haven't noticed such an announcement.

> I'm hoping to improve the maintenance in the near future.

 Well, if you have resources for doing that, it will be most welcomed.

  Maciej

<Prev in Thread] Current Thread [Next in Thread>