public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Martin.Jansa at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29249] csu/libc-tls.c:202: undefined reference to `_startup_fatal_not_constant' Date: Sat, 13 Aug 2022 12:34:16 +0000 [thread overview] Message-ID: <bug-29249-131-wV1tRQcgUe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29249-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29249 --- Comment #11 from Martin Jansa <Martin.Jansa at gmail dot com> --- Thanks H.J. Lu, I've verified that this patch works in my environment. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-13 12:34 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-15 6:06 [Bug libc/29249] New: " james.hilliard1 at gmail dot com 2022-06-15 7:11 ` [Bug libc/29249] " fweimer at redhat dot com 2022-06-15 7:18 ` james.hilliard1 at gmail dot com 2022-06-15 7:22 ` fweimer at redhat dot com 2022-06-15 7:47 ` james.hilliard1 at gmail dot com 2022-06-15 7:56 ` fweimer at redhat dot com 2022-06-15 8:07 ` james.hilliard1 at gmail dot com 2022-07-27 11:23 ` Martin.Jansa at gmail dot com 2022-08-03 19:10 ` rwmacleod at gmail dot com 2022-08-07 13:53 ` Martin.Jansa at gmail dot com 2022-08-08 10:28 ` yann at droneaud dot fr 2022-08-09 10:44 ` Martin.Jansa at gmail dot com 2022-08-09 19:03 ` hjl.tools at gmail dot com 2022-08-13 12:34 ` Martin.Jansa at gmail dot com [this message] 2022-09-22 16:38 ` koutheir at gmail dot com 2022-11-03 11:25 ` nsz at gcc dot gnu.org 2022-11-03 11:44 ` fweimer at redhat dot com 2022-11-03 15:02 ` fweimer at redhat dot com 2022-11-03 16:29 ` fweimer at redhat 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-29249-131-wV1tRQcgUe@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).