From: Mike Frysinger <vapier@gentoo.org>
To: Roland McGrath <roland@hack.frob.com>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] hppa: add missing prlimit64 symbol
Date: Sat, 11 Aug 2012 19:27:00 -0000 [thread overview]
Message-ID: <201208111527.37505.vapier@gentoo.org> (raw)
In-Reply-To: <20120413035854.BF0642C079@topped-with-meat.com>
[-- Attachment #1: Type: Text/Plain, Size: 1616 bytes --]
On Thursday 12 April 2012 23:58:54 Roland McGrath wrote:
> > sysdeps/unix/sysv/linux/wordsize-64/syscalls.list lists it
> > unconditionally (for the alias), and from there, it seems that all the
> > 32bit arches add it to their arch-specific list.
>
> That should mean that adding it to sysdeps/unix/sysv/linux/syscalls.list
> should do the right thing for hppa, and that removing it from other
> machine-specific syscalls.list files will then have no effect on the status
> quo. Can you try that and verify?
ok, i confused myself. wordsize-64/syscalls.list has the line:
prlimit EXTRA prlimit64 i:iipp prlimit prlimit64
while the 32bit arches have:
prlimit64 EXTRA prlimit64 i:iipp prlimit64
and additionally, we have:
sysdeps/unix/sysv/linux/prlimit.c
so if we try to build a 64bit system with both these syscalls.list entries, we
hit a build error:
/usr/local/src/gnu/glibc/build/x86_64/libc_pic.a(prlimit64.os): In function
`prlimit64':
/usr/local/src/gnu/glibc/misc/../sysdeps/unix/syscall-template.S:81: multiple
definition of `__GI_prlimit64'
/usr/local/src/gnu/glibc/build/x86_64/libc_pic.a(prlimit.os):/usr/local/src/gnu/glibc/misc/../sysdeps/unix/syscall-
template.S:81: first defined here
which makes sense as normally we don't generate a prlimit64 file at all, just a
prlimit wrapper with a prlimit64 alias in it.
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.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-11 19:27 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 [this message]
2012-08-12 12:59 ` Joseph S. Myers
2012-08-12 13:15 ` Carlos O'Donell
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=201208111527.37505.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
/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).