public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at acm dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/27596] bits/libc-header-start.h is C++ header-unit unfriendly
Date: Thu, 18 Mar 2021 11:35:03 +0000 [thread overview]
Message-ID: <bug-27596-131-f943QfgV2e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27596-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27596
Nathan Sidwell <nathan at acm dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Nathan Sidwell <nathan at acm dot org> ---
thanks Joseph, Yeah I noticed the lack of #if guarding, but forgot to mention.
This is indeed a 'non-importable header', and must be treated as text on each
inclusion. We'll mark it so in our builds.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-03-18 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 13:35 [Bug build/27596] New: " nathan at acm dot org
2021-03-17 20:36 ` [Bug build/27596] " joseph at codesourcery dot com
2021-03-18 11:35 ` nathan at acm 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-27596-131-f943QfgV2e@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: link
Be 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).