public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28595] New: 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 05:25:42 +0000 [thread overview] Message-ID: <bug-28595-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28595 Bug ID: 28595 Summary: 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) Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: sam at gentoo dot org CC: drepper.fsp at gmail dot com Target Milestone: --- This is a forward of a downstream report in Gentoo: https://bugs.gentoo.org/823780, although I've hit it myself. Building glibc-2.34 fails with the following error: ``` /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-r1/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 make[2]: *** [../Rules:269: /var/tmp/portage/sys-libs/glibc-2.34-r1/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ldconfig] Error 1 ``` In the bug, someone observed that it may be AVX512 related which matches my experience (I can only make the build fail on a Tiger Lake system). -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-11-15 5:25 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 5:25 sam at gentoo dot org [this message] 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 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@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: linkBe 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).