public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Native build fails in winsup/cygwin/libc/strptime.cc because of strtou?l_l()
Date: Wed, 24 Aug 2016 18:39:00 -0000	[thread overview]
Message-ID: <929a5346-a4e1-99f0-fe63-5c1bca7cdd30@t-online.de> (raw)
In-Reply-To: <20160824082813.GB1493@calimero.vinschen.de>

Am 24.08.2016 um 10:28 schrieb Corinna Vinschen:
> On Aug 24 00:19, Hans-Bernhard Bröker wrote:
>> Hello everyone,
>>
>> building the git version of cygwin natively on Cygwin-2.5.3, I'm running
>> into a problem with strtoul_l / strtol_l. winsup/cygwin/libc/strptime.cc
>> fails to build:
>> [...]
>>
>> Looking at the .ii file, it appears __GNU_VISIBLE is not active for this C++
>> source file?
>
> Yes, we discussed this already yesterday on the Freenode #cygwin-developers
> IRC channel.  The reason is that sys/cdefs.h is included before winsup.h
> is included, the latter defining _GNU_SOURCE.

Ah, yes.  That would do it.  The build does indeed work now, with the 
fix in git.  Thanks.

[...]
> That's pretty weird since _GNU_SOURCE is not supposed to be defined
> by the compiler or C preprocessor at all.

Well, it could be the specs file "contributing" it...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2016-08-24 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24  0:22 Hans-Bernhard Bröker
2016-08-24  8:38 ` Corinna Vinschen
2016-08-24 18:39   ` Hans-Bernhard Bröker [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=929a5346-a4e1-99f0-fe63-5c1bca7cdd30@t-online.de \
    --to=hbbroeker@t-online.de \
    --cc=cygwin@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).