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 build/31315] Build failure with gcc 6.4.1 in sunrpc/netname.c Date: Mon, 29 Jan 2024 22:13:01 +0000 [thread overview] Message-ID: <bug-31315-131-SJQ0PwvaE0@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31315-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31315 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.37 Status|ASSIGNED |RESOLVED Summary|Build failure with gcc |Build failure with gcc |6.4.1 |6.4.1 in sunrpc/netname.c Resolution|--- |FIXED --- Comment #2 from Florian Weimer <fweimer at redhat dot com> --- Fix backported: commit 8b8a3f0aafa30510abc5809db99c026af9a48016 Author: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> Date: Mon Jul 24 14:15:23 2023 -0300 sunrpc: Fix netname build with older gcc The -Wformat-overflow was added by gcc 8. Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 0eb6b2725ba4aae73c03ac1f05c31cd2a073c99a) Please add a comment if it doesn't work for you. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-29 22:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-29 19:17 [Bug build/31315] New: Build failure with gcc 6.4.1 skpgkp1 at gmail dot com 2024-01-29 21:23 ` [Bug build/31315] " fweimer at redhat dot com 2024-01-29 22:13 ` fweimer at redhat dot com [this message] 2024-01-30 0:01 ` [Bug build/31315] Build failure with gcc 6.4.1 in sunrpc/netname.c skpgkp1 at gmail dot com 2024-01-30 0:02 ` skpgkp1 at gmail 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-31315-131-SJQ0PwvaE0@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).