public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pavel.morozkin at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29132] If <stdc-predef.h> is not preincluded, then #define __STDC_xxx violate C11 6.10.8
Date: Tue, 10 May 2022 19:28:23 +0000	[thread overview]
Message-ID: <bug-29132-131-Dz20USdnuU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29132-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29132

--- Comment #5 from Pavel M <pavel.morozkin at gmail dot com> ---
The users expect the absence of C standard violations. The "non-GCC with glibc"
developers very probably don't know that <stdc-predef.h> needs to be
preincluded. Consider at least documenting it in "using glibc with non-GCC" (or
other similar) guide.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-05-10 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 10:58 [Bug libc/29132] New: " pavel.morozkin at gmail dot com
2022-05-09 11:31 ` [Bug libc/29132] " fweimer at redhat dot com
2022-05-09 11:49 ` schwab@linux-m68k.org
2022-05-09 16:43 ` pavel.morozkin at gmail dot com
2022-05-09 18:54 ` joseph at codesourcery dot com
2022-05-10 19:28 ` pavel.morozkin at gmail dot com [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-29132-131-Dz20USdnuU@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).