public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29130] error: #error "Assumed value of MB_LEN_MAX wrong" Date: Mon, 09 May 2022 11:29:29 +0000 [thread overview] Message-ID: <bug-29130-131-gjoGzWKi1s@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29130-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29130 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-05-09 Component|build |libc Status|UNCONFIRMED |WAITING CC| |drepper.fsp at gmail dot com, | |fweimer at redhat dot com Ever confirmed|0 |1 Flags| |security- --- Comment #3 from Florian Weimer <fweimer at redhat dot com> --- Can you reproduce the issue without gnulib headers? I see gnulib/wchar.h references in attachment 14095. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-09 11:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-08 20:49 [Bug build/29130] New: " euloanty at live dot com 2022-05-08 20:49 ` [Bug build/29130] " euloanty at live dot com 2022-05-08 20:50 ` euloanty at live dot com 2022-05-08 20:51 ` euloanty at live dot com 2022-05-08 20:52 ` euloanty at live dot com 2022-05-09 11:29 ` fweimer at redhat dot com [this message] 2022-05-09 13:32 ` [Bug libc/29130] " euloanty at live dot com 2022-05-11 12:51 ` 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-29130-131-gjoGzWKi1s@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).