From: Jim Blandy <jimb@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: rda@sources.redhat.com
Subject: Re: RFA: #define _GNU_SOURCE to get strsignal prototoype
Date: Thu, 07 Oct 2004 19:11:00 -0000 [thread overview]
Message-ID: <vt2r7oaqr7c.fsf@zenia.home> (raw)
In-Reply-To: <20041007091109.7177ed53@saguaro>
Kevin Buettner <kevinb@redhat.com> writes:
> On 07 Oct 2004 11:08:01 -0500
> Jim Blandy <jimb@redhat.com> wrote:
>
> > This removes some compilation warnings on older Red Hat systems.
> > #defining _GNU_SOURCE is the documented way to get these declarations
> > from GNU C Library header files. From "(libc) Feature Test Macros":
> >
> > You should define these macros by using `#define' preprocessor
> > directives at the top of your source code files. These directives
> > _must_ come before any `#include' of a system header file. It is best
> > to make them the very first thing in the file, preceded only by
> > comments. You could also use the `-D' option to GCC, but it's better
> > if you make the source files indicate their own meaning in a
> > self-contained way.
> >
> > ...
> >
> > - Macro: _GNU_SOURCE
> > If you define this macro, everything is included: ISO C89,
> > ISO C99, POSIX.1, POSIX.2, BSD, SVID, X/Open, LFS, and GNU
> > extensions. In the cases where POSIX.1 conflicts with BSD, the
> > POSIX definitions take precedence.
> >
> > 2004-09-24 Jim Blandy <jimb@redhat.com>
> >
> > * samples/async.c: #define _GNU_SOURCE before #including any
> > files, to get prototypes for GNU-specific functions like
> > strsignal.
>
> Okay.
Committed, thanks.
prev parent reply other threads:[~2004-10-07 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 16:08 Jim Blandy
2004-10-07 16:11 ` Kevin Buettner
2004-10-07 19:11 ` Jim Blandy [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=vt2r7oaqr7c.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=kevinb@redhat.com \
--cc=rda@sources.redhat.com \
/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).