This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] hppa: add missing prlimit64 symbol


On Sun, Aug 12, 2012 at 8:59 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Sat, 11 Aug 2012, Mike Frysinger wrote:
>
>> while the 32bit arches have:
>> prlimit64   EXTRA   prlimit64   i:iipp  prlimit64
>
>> so the next thing i tried was creating
>> sysdeps/unix/sysv/linux/wordsize-32/syscalls.list and adding the new prlimit
>> alias there.  but a simple i686 build doesn't pick up the new location of the
>> prlimit64 symbol.
>
> Well, it wouldn't be an *alias*; it would be the prlimit64 entry above.
> But, if the point is to fix things for hppa then you need to arrange for
> hppa to get a GLIBC_2.17 version for prlimit64, not the default GLIBC_2.13
> since in fact the function was missing in 2.13 for hppa - as noted in
> point (v) for hppa in my list at
> <http://sourceware.org/ml/libc-ports/2012-06/msg00048.html>.  (The lack of
> ABI baselines - which of course ought to be checked against binaries of
> old releases when set up - is point (g) on that list, and (x) is another
> point involving checks against old binaries.)
>
> (Adding the entry, but with @@GLIBC_2.17 like the SH fanotify_mark, to the
> hppa syscalls.list along with an appropriate Versions entry, is certainly
> the safer approach than doing something with the potential to affect other
> architectures, even though it may also be good to work out how to clean
> these things up.  Note hppa also needs fanotify_mark at a new version, and
> note that cleanups here only help existing architectures; there are no
> issues for new architectures using linux-generic because linux-generic
> already has the right entries in syscalls.list.)

I've been spending the weekend bringing up new hardware for my hppa
testing, so hopefully I can get back to tackling the maintenance
backlog (along with any 2.15 and 2.16 backport requests).

Cheers,
Carlos.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]