linux-mips
[Top] [All Lists]

Re: GLIBC moved mips to Ports

To: Jim Gifford <maillist@jg555.com>
Subject: Re: GLIBC moved mips to Ports
From: Daniel Jacobowitz <dan@debian.org>
Date: Tue, 21 Feb 2006 09:42:11 -0500
Cc: Linux MIPS List <linux-mips@linux-mips.org>
In-reply-to: <43FA8F04.3040606@jg555.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <43FA8F04.3040606@jg555.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.8i
On Mon, Feb 20, 2006 at 07:54:44PM -0800, Jim Gifford wrote:
> Just an FYI, I've been working trying to keep MIPS updated in glibc. 
> Again some changes were made that broke the MIPS build with the current 
> snapshot. I guess all of Daniel's and my work just got thrown away. As 
> of today MIPS is no longer going to be support in trunk. Here's the 
> message I received today.
> 
> In my opinion this seems to mean that MIPS is not a high priority in 
> their book.
> 
> ------- Additional Comments From roland at gnu dot org  2006-02-21 02:14 
> -------
> For the trunk, mips has moved to the ports repository.
> Daniel should be able to commit his fixes there directly.
> Items needing merge in the 2.3 branch can be reassigned to me.

Sigh.  Jim, you are slightly misinterpreting this.

MIPS has _never_ been a high priority of the glibc maintainers.  What
happened here is that they admitted it - and moved it to a separate
repository so that (A) they don't need to deal with it, and (B) people
who are interested can deal with it.  It's unfortunate, but realistic.

The ports repository is going to continue to be supported and we're
going to keep it working.  We just have to do the legwork.  I'll go
over the MIPS build fixes this week sometime.

-- 
Daniel Jacobowitz
CodeSourcery

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