This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: glibc am33 and cris architectures
- From: Mark Salter <msalter at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, libc-ports at sourceware dot org, hp at axis dot com
- Date: Tue, 27 Mar 2012 09:34:20 -0400
- Subject: Re: glibc am33 and cris architectures
- References: <Pine.LNX.4.64.1202211504050.16457@digraph.polyomino.org.uk> <orr4wtnp8g.fsf@livre.localdomain> <Pine.LNX.4.64.1203261707270.17052@digraph.polyomino.org.uk>
On Mon, 2012-03-26 at 17:09 +0000, Joseph S. Myers wrote:
> On Fri, 16 Mar 2012, Alexandre Oliva wrote:
>
> > I've long been out of touch WRT am33, but I finally brought this up
> > within Red Hat folks that are involved with it.
> >
> > Mark Salter volunteered to contribute the updates he'd worked on, but
> > that had failed to be contributed because I failed to review the TLS
> > support patches for GCC and binutils (sorry)
> >
> > So, instead of removing the port, I suggest we name Mark maintainer of
> > the am33 port. Any objections?
>
> I haven't seen any objections; obviously some pretty large patches will be
> needed to bring the port up to date, replace the Linuxthreads port by an
> NPTL port and generally update sysdeps files for several years of libc
> changes that involve all-targets updates, so they are in sync with the
> libc versions again. And then he'll need to keep a watch on libc commits
> for any that require am33 updates to keep am33 in sync, and make such
> updates to the port as and when such libc commits are made.
>
I have patches which add NPTL to glibc 2.9 and I'm in the process of
bringing those forward to the devel head. And yes, going forward I
intend to keep an eye on the glibc devel and add am33 glibc to the
things I regularly build and test.
--Mark