From: Joseph Myers <joseph@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
<gcc-patches@gcc.gnu.org>, <bug-hurd@gnu.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH] Hurd: Enable ifunc by default
Date: Mon, 18 Jan 2021 20:05:44 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2101182003160.272665@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87h7nl1425.fsf@dem-tschwing-1.ger.mentorg.com>
On Wed, 13 Jan 2021, Thomas Schwinge wrote:
> Hi!
>
> Thanks (and sorry for the delay), pushed "Hurd: Enable ifunc by default"
> to master branch in commit e9cb89b936f831a02318d45fc4ddb06f7be55ae4, and
> cherry-picked into releases/gcc-10 branch in commit
> 92b131491c22eb4e4b663d226e9d97f1fd693063, releases/gcc-9 branch in commit
> 0313ce139f4ca3c96db9dc82125ec9e4a167a224, releases/gcc-8 branch in commit
> 975b0fa0f43e84bed3cb1b2b593132bc219f962c, see attached.
I'm not sure what toolchain component the underlying bug is in, but this
GCC commit (verified in the releases/gcc-10 case) results in a glibc build
failure for i686-gnu with build-many-glibcs.py.
https://sourceware.org/pipermail/libc-testresults/2021q1/007378.html
The error is:
/scratch/jmyers/glibc-bot/install/compilers/i686-gnu/lib/gcc/i686-glibc-gnu/11.0.0/../../../../i686-glibc-gnu/bin/ld: /scratch/jmyers/glibc-bot/build/compilers/i686-gnu/glibc/i686-gnu/elf/librtld.os: in function `hurd_file_name_lookup_retry':
(.text+0x1e08e): undefined reference to `strncpy'
collect2: error: ld returned 1 exit status
Makefile:584: recipe for target '/scratch/jmyers/glibc-bot/build/compilers/i686-gnu/glibc/i686-gnu/elf/ld.so' failed
make[3]: *** [/scratch/jmyers/glibc-bot/build/compilers/i686-gnu/glibc/i686-gnu/elf/ld.so] Error 1
--
Joseph S. Myers
joseph@codesourcery.com
next parent reply other threads:[~2021-01-18 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201108225251.3195591-1-samuel.thibault@ens-lyon.org>
[not found] ` <87h7nl1425.fsf@dem-tschwing-1.ger.mentorg.com>
2021-01-18 20:05 ` Joseph Myers [this message]
2021-01-18 20:25 ` Samuel Thibault
2021-01-19 0:04 ` Samuel Thibault
2021-01-19 0:17 ` H.J. Lu
2021-01-19 0:21 ` Samuel Thibault
2021-01-19 0:24 ` Samuel Thibault
2021-01-19 0:40 ` H.J. Lu
2021-01-19 2:24 ` [PATCH] Hurd: Add rtld-strncpy-c.c H.J. Lu
2021-01-19 9:02 ` Samuel Thibault
2021-01-19 12:21 ` H.J. Lu
2021-01-19 12:25 ` Adhemerval Zanella
2021-01-19 12:35 ` H.J. Lu
2021-01-19 12:44 ` 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=alpine.DEB.2.22.394.2101182003160.272665@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bug-hurd@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=thomas@codesourcery.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).