From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: A small issue with _GNU_SOURCE
Date: Tue, 17 Feb 2015 21:43:00 -0000 [thread overview]
Message-ID: <20150217214346.GE8493@calimero.vinschen.de> (raw)
In-Reply-To: <54E38776.1030707@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
On Feb 17 18:24, Jon TURNEY wrote:
>
> Consider the following:
>
> $ cat test.c
> #include <string.h>
> #include <stdlib.h>
>
> int main()
> {
> long long i = random();
> return ffsll(i);
> }
>
> ffsll() is a GNU extension and should be prototyped when _GNU_SOURCE is
> defined.
>
> random() is in SUSv2 and requires _XOPEN_SOURCE=500
>
> $ gcc test.c -Wall -ansi -D_XOPEN_SOURCE=700
> test.c: In function ‘main’:
> test.c:8:2: warning: implicit declaration of function ‘ffsll’
>
> This is correct
>
> $ gcc test.c -Wall -ansi -D_XOPEN_SOURCE=700 -D_GNU_SOURCE
> test.c: In function ‘main’:
> test.c:8:2: warning: implicit declaration of function ‘ffsll’
>
> This looks like a problem with newlib's sys/cdefs.h. _XOPEN_SOURCE causes
> _POSIX_C_SOURCE to be defined, which prevents _GNU_SOURCE from being
> considered.
>
> $ gcc test.c -Wall -ansi -D_GNU_SOURCE
> test.c: In function ‘main’:
> test.c:7:2: warning: implicit declaration of function ‘random’
>
> _GNU_SOURCE is supposed to imply some value of _XOPEN_SOURCE, but only
> actually turns on __XSI_VISIBLE.
>
> The patch I wrote for cygwin's stdlib.h [1] explicitly checks _XOPEN_SOURCE.
> Should this be a check for XSI_VISIBLE? or should cdefs.h also define
> _XOPEN_SOURCE (and all the other feature test macros that _GNU_SOURCE is
> defined to be equivalent to)?
The check should be one for XSI_VISIBLE. I'm not sure about cdefs.h,
though. Maybe you want to ask the question on the newlib ML? I'll
look into it tomorrow.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-02-17 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54E3808B.9040302@dronecode.org.uk>
2015-02-17 18:25 ` Fwd: " Jon TURNEY
2015-02-17 21:43 ` Corinna Vinschen [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=20150217214346.GE8493@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@cygwin.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).