public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2677: Need something to #ifdef on when -pedantic/-pedantic-errors
Date: Sat, 28 Apr 2001 12:56:00 -0000	[thread overview]
Message-ID: <20010428195600.29122.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c/2677; it has been noted by GNATS.

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <rfg@monkeys.com>
Cc: <gcc-gnats@gcc.gnu.org>,  <gcc-bugs@gcc.gnu.org>
Subject: Re: c/2677: Need something to #ifdef on when -pedantic/-pedantic-errors
Date: Sat, 28 Apr 2001 20:55:32 +0100 (BST)

 On 28 Apr 2001 rfg@monkeys.com wrote:
 
 > Build and install the glib library (version 1.2 or 1.3.4)
 > and associated include files.  Then compile something that
 > includes "glib.h" and do so while using the -pedantic or
 > -pedantic-errors option.  You'll get warnings or errors,
 > respectively, because glib.h uses the non-standard GNU
 > notation for macros accepting variable numbers of arguments.
 
 3.0 does not give these warnings for system headers, or macros defined in
 system headers.
 
 (You'll need to ensure that the glib headers do count as system headers,
 e.g. by adding
 
 #if defined(__GNUC__) && (__GNUC__ > 2 || __GNUC_MINOR >= 97)
 #pragma GCC system_header
 #endif
 
 .)
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2001-04-28 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-28 12:56 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-28 14:16 Zack Weinberg
2001-04-28 13:56 Joseph S. Myers
2001-04-28 13:36 Ronald F. Guilmette
2001-04-28 12:46 rfg

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=20010428195600.29122.qmail@sourceware.cygnus.com \
    --to=jsm28@cam.ac.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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).