public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: cs720 Administrator <cs720@cisunix.unh.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/7988: POSIX broken in gcc
Date: Fri, 20 Sep 2002 12:06:00 -0000	[thread overview]
Message-ID: <20020920190601.27617.qmail@sources.redhat.com> (raw)

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

From: cs720 Administrator <cs720@cisunix.unh.edu>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: cs720@unh.edu, <gcc-gnats@gcc.gnu.org>, <rdr@unh.edu>, <pas@unh.edu>
Subject: Re: preprocessor/7988: POSIX broken in gcc
Date: Fri, 20 Sep 2002 15:00:20 -0400 (EDT)

 Neil:
 
 I wasn't sure how to categorize it --
 _POSIX_C_SOURCE is a preprocessor symbol and it
 is used to select header files, define other symbols
 and structures, etc.  Defining it selects one set
 of headers, etc. while not defining it selects
 another set.  Perhaps the error is in the
 organization of the header files themselves,
 and the use of _POSIX_C_SOURCE within those header files.
 I doubt it is in the preprocessor itself, but
 what other category would be better?
 
 Thanks,
 Bob Russell
 
 
 On Fri, 20 Sep 2002, Neil Booth wrote:
 
 > cs720@unh.edu wrote:-
 >
 > > >Number:         7988
 > > >Category:       preprocessor
 > > >Synopsis:       Programs defining _POSIX_C_SOURCE compile but won't run
 >
 > So this has nothing to do with the preprocessor then?
 >
 > Neil.
 >
 


             reply	other threads:[~2002-09-20 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 12:06 cs720 Administrator [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-04 11:56 Neil Booth
2002-09-20 10:26 Neil Booth
2002-09-20  8:06 cs720

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=20020920190601.27617.qmail@sources.redhat.com \
    --to=cs720@cisunix.unh.edu \
    --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).