From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
Roland McGrath <roland@hack.frob.com>,
libc-ports@sourceware.org
Subject: Re: [PATCH] hppa: add missing prlimit64 symbol
Date: Sun, 12 Aug 2012 13:15:00 -0000 [thread overview]
Message-ID: <CADZpyixTwCs2Buhqo7oEW9A9XEHSE1SuAS-Pz7RK9O-_ggYdbg@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1208121250390.30885@digraph.polyomino.org.uk>
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.
next prev parent reply other threads:[~2012-08-12 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 23:00 Mike Frysinger
2012-04-12 23:07 ` Roland McGrath
2012-04-12 23:26 ` Mike Frysinger
2012-04-13 3:59 ` Roland McGrath
2012-08-11 19:27 ` Mike Frysinger
2012-08-12 12:59 ` Joseph S. Myers
2012-08-12 13:15 ` Carlos O'Donell [this message]
2012-08-12 16:03 ` Joseph S. Myers
2012-08-12 14:48 ` Mike Frysinger
2012-08-12 14:51 ` Carlos O'Donell
2012-08-12 15:58 ` Joseph S. Myers
2012-08-12 15:00 ` Mike Frysinger
2012-04-13 2:00 ` Carlos O'Donell
2012-04-13 2:02 ` Carlos O'Donell
2012-04-13 2:21 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADZpyixTwCs2Buhqo7oEW9A9XEHSE1SuAS-Pz7RK9O-_ggYdbg@mail.gmail.com \
--to=carlos@systemhalted.org \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).