public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at zx2c4 dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/28595] glibc-2.34 build fails with linker error (TLS transition from R_386_TLS_GOTIE to R_386_TLS_LE_32 against `__libc_tsd_CTYPE_B' at 0xf4 in section `.text' failed)
Date: Mon, 15 Nov 2021 13:38:42 +0000 [thread overview]
Message-ID: <bug-28595-131-ns1zDNiDTg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28595-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28595
Jason A. Donenfeld <jason at zx2c4 dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at zx2c4 dot com
--- Comment #5 from Jason A. Donenfeld <jason at zx2c4 dot com> ---
Pulling from the downstream bug report:
> -march=tigerlake - ERROR
> -march=cooperlake - ERROR
> -march=cascadelake - ERROR
> -march=cannonlake - ERROR
> -march=skylake-avx512 - ERROR
> -march=skylake - OK
And from my own failure, I noticed that this is hit during the -m32 build. I
don't know whether that's a relevant detail, but it is a detail:
x86_64-pc-linux-gnu-gcc -m32 -march=native -pipe -O2 -Wl,-O1 -Wl,--as-needed
-nostdlib -nostartfiles -static -o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ldconfig
-Wl,-O1 -Wl,--as-needed
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/csu/crt1.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/csu/crti.o
`x86_64-pc-linux-gnu-gcc -m32 -march=native -pipe -O2 -Wl,-O1 -Wl,--as-needed
--print-file-name=crtbeginT.o`
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ldconfig.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/cache.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/readlib.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/xmalloc.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/xstrdup.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/chroot_canon.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/static-stubs.o
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/stringtable.o
-Wl,-z,now -Wl,--start-group
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc.a
-lgcc -Wl,--end-group `x86_64-pc-linux-gnu-gcc -m32 -march=native -pipe -O2
-Wl,-O1 -Wl,--as-needed --print-file-name=crtend.o`
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/csu/crtn.o
make[4]: Leaving directory
'/var/tmp/portage/sys-libs/glibc-2.34-r2/work/glibc-2.34/nptl'
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
/var/tmp/portage/sys-libs/glibc-2.34-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc.a(inet_addr.o):
TLS transition from R_386_TLS_GOTIE to R_386_TLS_LE_32 against
`__libc_tsd_CTYPE_B' at 0xf4 in section `.text' failed
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
final link failed: bad value
collect2: error: ld returned 1 exit status
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-15 13:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 5:25 [Bug libc/28595] New: " sam at gentoo dot org
2021-11-15 5:29 ` [Bug libc/28595] " sam at gentoo dot org
2021-11-15 5:30 ` sam at gentoo dot org
2021-11-15 5:35 ` [Bug build/28595] " sam at gentoo dot org
2021-11-15 5:36 ` sam at gentoo dot org
2021-11-15 9:09 ` schwab@linux-m68k.org
2021-11-15 13:38 ` jason at zx2c4 dot com [this message]
2021-11-15 13:53 ` jason at zx2c4 dot com
2021-11-15 13:59 ` jason at zx2c4 dot com
2021-11-15 14:02 ` jakub at redhat dot com
2021-11-15 14:14 ` jason at zx2c4 dot com
2021-11-15 14:24 ` jason at zx2c4 dot com
2021-11-15 14:28 ` jason at zx2c4 dot com
2021-11-15 19:29 ` fweimer at redhat dot com
2021-11-16 11:56 ` jason at zx2c4 dot com
2021-11-16 11:57 ` jason at zx2c4 dot com
2021-11-16 12:00 ` jason at zx2c4 dot com
2021-11-16 12:12 ` jason at zx2c4 dot com
2021-11-16 12:24 ` jason at zx2c4 dot com
2021-11-16 12:34 ` jakub at redhat dot com
2021-11-16 12:35 ` jakub at redhat dot com
2021-11-16 12:38 ` jakub at redhat dot com
2021-11-16 13:02 ` jason at zx2c4 dot com
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=bug-28595-131-ns1zDNiDTg@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).