This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: Ports status for 2.11 (was: Re: Will the alpha port be usable for 2.11?)
On Sun, 8 Nov 2009, Carlos O'Donell wrote:
> I've been working on the hppa port this weekend.
>
> > * HPPA. ?Maintained by Carlos. ?Needs ports files updates and
> > ____longjmp_chk implementation. ?One HPPA bug (6676) is marked with the
> > glibc_2.11 keyword.
>
> The ____longjmp_check implementation will be checked in by the end of today.
>
> The PIE fix will also be checked in by the end of today.
Thanks. What are your plans regarding miscellaneous sysdeps files that
have changed in libc over the past few years in ways that need
corresponding hppa updates? (bits/fcntl.h is one of the most frequently
changing, but probably not the only one. Some updates are perhaps less
obvious - for example, fallocate64 exports
<http://sourceware.org/ml/libc-hacker/2009-05/msg00003.html> or ensuring
that identifiers in headers that are not part of the public API, such as
parameter names, have their proper leading "__". Certainly for
fallocate64 you need to decide whether it is or is not exported at version
2.11.)
> Unforutnately in addition to this I had to implement the
> _STACK_GROWS_UP case for nptl/pthread_create.c, which is currently
> #error "to do", therefore the hppa port will never compile with 2.11
> because of this and upstream is already tagged.
We know neither HPPA nor M68K can work perfectly with 2.11 tag, simply
because the support for different libgcc_s sonames went into libc after
that tag (but before the branch), and M68K also needs elf.h changes. But
I'd hope they can work with future versions on 2.11 branch (whether or not
there is a 2.11.1 release).
--
Joseph S. Myers
joseph@codesourcery.com