public inbox for rda@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: rda@sources.redhat.com
Subject: RFA: #define _GNU_SOURCE to get strsignal prototoype
Date: Thu, 07 Oct 2004 16:08:00 -0000	[thread overview]
Message-ID: <vt2ekkazf32.fsf@zenia.home> (raw)


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.

Index: rda/samples/async.c
===================================================================
RCS file: /cvs/src/src/rda/samples/async.c,v
retrieving revision 1.1
diff -c -p -r1.1 async.c
*** rda/samples/async.c	28 Aug 2002 01:22:28 -0000	1.1
--- rda/samples/async.c	7 Oct 2004 16:03:08 -0000
***************
*** 22,27 ****
--- 22,29 ----
     Alternative licenses for RDA may be arranged by contacting Red Hat,
     Inc.  */
  
+ #define _GNU_SOURCE             /* enables strsignal prototype in <string.h> */
+ 
  #include "config.h"
  
  #include <stdio.h>

             reply	other threads:[~2004-10-07 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 16:08 Jim Blandy [this message]
2004-10-07 16:11 ` Kevin Buettner
2004-10-07 19:11   ` Jim Blandy

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=vt2ekkazf32.fsf@zenia.home \
    --to=jimb@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).