Re: glibc am33 and cris architectures

[Alexandre Oliva <aoliva@redhat.com>]

On Feb 21, 2012, "Joseph S. Myers" <joseph@codesourcery.com> wrote:

> The am33 and cris glibc ports won't have worked since the 2.3-2.5 era for 
> lack of NPTL/TLS support.  They are currently on the deprecation list for 
> removal after glibc 2.16 is released 
> <http://sourceware.org/glibc/wiki/Deprecation>.  But given how long they 
> won't have worked, I wonder if we should just remove them now.  Alexandre, 
> Hans-Peter - do you have, or know of, any near-term plans to bring your 
> respective ports up to date with NPTL and TLS support and updates for all 
> the other libc changes in the past several years?  If not, I think it's 
> time to remove them.  (Alexandre, since you have write access you can just 
> remove the am33 port yourself - "git rm" on the directories sysdeps/am33 
> sysdeps/unix/am33 sysdeps/unix/sysv/linux/am33 with an appropriate entry 
> in ChangeLog.am33.)

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?

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer