From: Stefan Liebler <stli@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [hurd,commited] hurd: Avoid more libc.so local PLTs
Date: Tue, 03 Apr 2018 09:02:00 -0000 [thread overview]
Message-ID: <95b0834b-d041-a4e5-ef47-97ae65fe1956@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180403082029.g3bfw4upbti67wwz@var.youpi.perso.aquilenet.fr>
On 04/03/2018 10:20 AM, Samuel Thibault wrote:
> Andreas Schwab, on mar. 03 avril 2018 10:10:21 +0200, wrote:
>> On Apr 03 2018, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
>>
>>> * hurd/catch-signal.c (__hurd_catch_signal): Call __libc_siglongjmp
>>> instead if siglongjmp.
>>> (hurd_safe_memmove): Call __libc_longjmp instead of longjmp.
>>> * hurd/hurdfault.c (faulted): Call __libc_longjmp instead of longjmp.
>>> * include/setjmp.h (__libc_siglongjmp, __libc_longjmp): New hidden
>>> prototypes.
>>> * libio/iolibio.h (_IO_puts): New hidden prototype.
>>> * libio/ioputs.c (_IO_puts): New hidden def.
>>> * setjmp/longjmp.c (__libc_longjmp, __libc_siglongjmp): New hidden
>>> defs.
>>> * sysdeps/mach/hurd/sigwait.c (__sigwait): Call __libc_longjmp instead
>>> of longjmp.
>>
>> https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/glibc/s/s390x
>>
>> In file included from <command-line>:0:0:
>> ../sysdeps/s390/longjmp.c:35:34: error: '__libc_longjmp' aliased to undefined symbol '__libc_siglongjmp'
>> strong_alias (__libc_siglongjmp, __libc_longjmp)
>> ^
>> ./../include/libc-symbols.h:135:26: note: in definition of macro '_strong_alias'
>> extern __typeof (name) aliasname __attribute__ ((alias (#name)));
>> ^~~~~~~~~
>> ../sysdeps/s390/longjmp.c:35:1: note: in expansion of macro 'strong_alias'
>> strong_alias (__libc_siglongjmp, __libc_longjmp)
>
> Ah, there is #define __libc_siglongjmp magic here indeed. Does the
> attached patch fix it?
>
> Samuel
>
Yes. This patch fixes the issue on s390x.
Thanks.
Stefan
next prev parent reply other threads:[~2018-04-03 9:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 0:38 Samuel Thibault
2018-04-03 8:10 ` Andreas Schwab
2018-04-03 8:20 ` Samuel Thibault
2018-04-03 9:02 ` Stefan Liebler [this message]
2018-04-03 19:26 ` H.J. Lu
2018-04-03 20:51 ` H.J. Lu
2018-04-03 21:08 ` Samuel Thibault
2018-04-03 21:16 ` H.J. Lu
2018-04-03 21:24 ` Samuel Thibault
2018-04-03 21:41 ` H.J. Lu
2018-04-03 21:55 ` Samuel Thibault
2018-04-03 22:14 ` H.J. Lu
2018-04-03 22:18 ` Samuel Thibault
2018-04-03 22:21 ` H.J. Lu
2018-04-03 22:30 ` Samuel Thibault
2018-04-03 22:21 ` Zack Weinberg
2018-04-03 22:28 ` Samuel Thibault
2018-04-03 22:33 ` Zack Weinberg
2018-04-04 7:20 ` Andreas Schwab
2018-04-03 22:39 ` Samuel Thibault
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=95b0834b-d041-a4e5-ef47-97ae65fe1956@linux.vnet.ibm.com \
--to=stli@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.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).