public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/29162] [PATCH] string.h syntactic error: include/bits/string_fortified.h:110: error: expected ',' or ';' before '__fortified_attr_access' Date: Mon, 23 May 2022 08:42:44 +0000 [thread overview] Message-ID: <bug-29162-131-B4DDxtl1zR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29162-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29162 Siddhesh Poyarekar <siddhesh at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.36 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Siddhesh Poyarekar <siddhesh at sourceware dot org> --- Fixed in master, 2.35 and 2.34. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-05-23 8:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-20 14:59 [Bug string/29162] New: " slyich at gmail dot com 2022-05-20 15:07 ` [Bug string/29162] " slyich at gmail dot com 2022-05-23 8:42 ` siddhesh at sourceware dot org [this message]
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-29162-131-B4DDxtl1zR@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).