public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30371] C2x strtol binary constant handling is incomplete Date: Mon, 22 May 2023 16:42:43 +0000 [thread overview] Message-ID: <bug-30371-131-HpUuYlMy3C@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30371-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30371 eggert at cs dot ucla.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eggert at cs dot ucla.edu --- Comment #4 from eggert at cs dot ucla.edu --- I installed the following patch to Gnulib: https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=3ad52f3e21db96096105256ff66ebf480703a09f This should work around this glibc bug in applications that use Gnulib. However, these applications will compile their own substitutes for strtol etc. It'd be better to fix this in glibc. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-22 16:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-18 17:44 [Bug libc/30371] New: " bruno at clisp dot org 2023-04-18 19:42 ` [Bug libc/30371] " kdudka at redhat dot com 2023-04-18 21:08 ` eblake at redhat dot com 2023-04-18 21:13 ` eblake at redhat dot com 2023-04-18 21:42 ` bruno at clisp dot org 2023-04-19 2:46 ` sam at gentoo dot org 2023-04-20 14:58 ` mliska at suse dot cz 2023-05-22 16:42 ` eggert at cs dot ucla.edu [this message] 2023-07-03 20:14 ` bruno at clisp dot org
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-30371-131-HpUuYlMy3C@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).