public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Mike Coleman <mkc+dated+1028693179.d6e9b5@mathdogs.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/6126: Tru64 5.1 doesn't expose stat(2) as a function
Date: Mon, 22 Jul 2002 21:16:00 -0000	[thread overview]
Message-ID: <20020723041601.18850.qmail@sources.redhat.com> (raw)

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

From: Mike Coleman <mkc+dated+1028693179.d6e9b5@mathdogs.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, mkc@stowers-institute.org
Cc:  
Subject: Re: c/6126: Tru64 5.1 doesn't expose stat(2) as a function 
Date: Tue, 23 Jul 2002 04:06:19 GMT

 With rth's addition of the 'extern_prefix' pragma, a simple way to now exists
 to fix sys/stat.h on Tru64 5.1, which is to just add
 
 #define _LIBC_POLLUTION_H_
 
 somewhere early in the file.  This will prevent stat and friends from being
 defined as macros and cause the extern_prefix pragma to be used instead.
 
 
 The define above probably ought to be added after the includes.  Here's a
 snippet from that area.  Maybe someone that knows fixincludes could whip up a
 little pattern.
 
 Mike
 
 [from sys/stat.h:]
 
 
 #include <standards.h>
 #include <sys/types.h>
 #include <sys/mode.h>
 
 #if defined(__cplusplus)
 extern "C"
 {
 #endif
 
 
 
 
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6126


             reply	other threads:[~2002-07-23  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22 21:16 Mike Coleman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23  0:40 rth
2002-04-01 17:35 rth

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=20020723041601.18850.qmail@sources.redhat.com \
    --to=mkc+dated+1028693179.d6e9b5@mathdogs.com \
    --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).