From: Jonathan Nieder <jrnieder@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org, ramsay@ramsay1.demon.co.uk
Subject: Re: [PATCH RFC] CYGWIN: avoid implicit declaration warning
Date: Mon, 24 Nov 2014 09:59:47 -0800 [thread overview]
Message-ID: <20141124175947.GN6527@google.com> (raw)
In-Reply-To: <5471EC26.3040705@web.de>
Torsten Bögershausen wrote:
> gcc under cygwin reports several warnings like this:
>
> warning: implicit declaration of function 'memmem'
> [-Wimplicit-function-declaration]
>
> This has been observed under CYGWIN-32 with GCC 4.7.3 as well
> as CYGWIN-64 with gcc v4.8.3-5 x86-64
>
> Do not #define _XOPEN_SOURCE 600 for CYGWIN.
>
> Reported-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
> Signed-off-by: Torsten Bögershausen <tboegi@web.de>
> ---
> This may be a start for a patch, tested under CYGWIN-32,
> both Windows7 and XP
The "tested under" part would also be a good addition to the commit
message.
> git-compat-util.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Patch looks good to me. Do you know if this has been reported to the
Cygwin maintainers? The behavior seems counterintuitive --- I would
expect _GNU_SOURCE to override everything else (since I thought that
was the point of _GNU_SOURCE).
Thanks,
Jonathan
next prev parent reply other threads:[~2014-11-24 17:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 14:16 [PATCH RFC] CYGWIN: avoid implicit declaration warning Torsten Bögershausen
2014-11-23 17:12 ` Ramsay Jones
2014-11-23 18:53 ` Junio C Hamano
2014-11-23 23:15 ` Ramsay Jones
2014-11-24 7:20 ` Torsten Bögershausen
2014-11-24 16:00 ` Torsten Bögershausen
2014-11-24 18:29 ` [PATCH] t5000 on Windows: do not mistake "sh.exe" as "sh" Johannes Sixt
2014-11-24 20:02 ` Torsten Bögershausen
2014-11-24 21:27 ` [PATCH RFC] CYGWIN: avoid implicit declaration warning Ramsay Jones
2014-11-24 21:44 ` Junio C Hamano
2014-11-24 22:59 ` Ramsay Jones
2014-11-24 22:27 ` Ramsay Jones
2014-11-24 22:50 ` Junio C Hamano
2014-11-24 23:04 ` Ramsay Jones
2014-11-24 17:59 ` Jonathan Nieder [this message]
2014-11-24 19:17 ` Torsten Bögershausen
2014-11-24 21:41 ` Ramsay Jones
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=20141124175947.GN6527@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=tboegi@web.de \
/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 NNTP newsgroup(s).