From: Samuel Thibault <sthibaul@sourceware.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [glibc] chk: Add and fix hidden builtin definitions for *_chk
Date: Fri, 4 Aug 2023 10:05:11 +0200 [thread overview]
Message-ID: <20230804080511.2u3neyxenqvvwpzv@begin> (raw)
In-Reply-To: <87o7jnqmp5.fsf@linux-m68k.org>
Ah, right, powerpc has its own longjmp.c. Now fixed.
Andreas Schwab, le ven. 04 août 2023 09:41:10 +0200, a ecrit:
> In file included from <command-line>:
> ../include/setjmp.h:19:20: error: redefinition of '__longjmp_chk'
> 19 | #define siglongjmp __longjmp_chk
> | ^~~~~~~~~~~~~
> ./../include/libc-symbols.h:155:26: note: in definition of macro '_weak_alias'
> 155 | extern __typeof (name) aliasname __attribute__ ((weak, alias (#name))) \
> | ^~~~~~~~~
> ../include/shlib-compat.h:117:3: note: in expansion of macro 'weak_alias'
> [ 135s] 117 | weak_alias (local, symbol)
> | ^~~~~~~~~~
> ../sysdeps/powerpc/longjmp.c:56:1: note: in expansion of macro 'versioned_symbol'
> 56 | versioned_symbol (libc, __vmx__libc_siglongjmp, siglongjmp, GLIBC_2_3_4);
> | ^~~~~~~~~~~~~~~~
> ../sysdeps/powerpc/longjmp.c:56:49: note: in expansion of macro 'siglongjmp'
> 56 | versioned_symbol (libc, __vmx__libc_siglongjmp, siglongjmp, GLIBC_2_3_4);
> | ^~~~~~~~~~
> ../include/setjmp.h:18:17: note: previous definition of '__longjmp_chk' with type 'void(struct __jmp_buf_tag *, int)'
> 18 | #define longjmp __longjmp_chk
> | ^~~~~~~~~~~~~
> ./../include/libc-symbols.h:155:26: note: in definition of macro '_weak_alias'
> 155 | extern __typeof (name) aliasname __attribute__ ((weak, alias (#name))) \
> | ^~~~~~~~~
> ../include/shlib-compat.h:117:3: note: in expansion of macro 'weak_alias'
> 117 | weak_alias (local, symbol)
> | ^~~~~~~~~~
> ../sysdeps/powerpc/longjmp.c:55:1: note: in expansion of macro 'versioned_symbol'
> 55 | versioned_symbol (libc, __vmx__libc_siglongjmp, longjmp, GLIBC_2_3_4);
> | ^~~~~~~~~~~~~~~~
> ../sysdeps/powerpc/longjmp.c:55:49: note: in expansion of macro 'longjmp'
> 55 | versioned_symbol (libc, __vmx__libc_siglongjmp, longjmp, GLIBC_2_3_4);
> | ^~~~~~~
> make[2]: *** [/home/abuild/rpmbuild/BUILD/glibc-2.38.9000.12.g04bf7d2d8a/cc-base/sysd-rules:1773: /home/abuild/rpmbuild/BUILD/glibc-2.38.9000.12.g04bf7d2d8a/cc-base/setjmp/longjmp.o] Error 1
prev parent reply other threads:[~2023-08-04 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230803204739.0A71A385783F@sourceware.org>
2023-08-04 7:41 ` Andreas Schwab
2023-08-04 8:05 ` Samuel Thibault [this message]
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=20230804080511.2u3neyxenqvvwpzv@begin \
--to=sthibaul@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).