From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: _GNU_SOURCE redundant define
Date: Mon, 18 Aug 2008 10:50:58 +0200 [thread overview]
Message-ID: <8763pyg0zx.fsf@ambire.localdomain> (raw)
In-Reply-To: <87skt3iaa9.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 17 Aug 2008 23:47:26 +0200")
() ludo@gnu.org (Ludovic Courtès)
() Sun, 17 Aug 2008 23:47:26 +0200
The "current Autoconf way" is to use `AC_USE_SYSTEM_EXTENSIONS'
Note that you should also reposition:
#include "libguile/_scm.h"
as the first #include (before <stdio.h> et al) in, for example,
libguile/stime.c, so that the system extension macros can DTRT.
thi
next prev parent reply other threads:[~2008-08-18 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 17:03 _GNU_SOURCE redundant define Greg Troxel
2008-08-13 21:30 ` Ludovic Courtès
2008-08-13 22:39 ` Greg Troxel
2008-08-14 7:54 ` Ludovic Courtès
2008-08-15 13:32 ` Greg Troxel
2008-08-17 21:47 ` Ludovic Courtès
2008-08-18 8:50 ` Thien-Thi Nguyen [this message]
2008-08-20 17:12 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8763pyg0zx.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).