DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Oe6ZXmzHi3pczS2X
	EIDXOqxgdxbmo8WxRHfOLjUFcs3mvnd6qls1XCIwZfljdUL/5KSJduY0ydu497Ys
	RwrczqHOTdM4LQSkkxdY8Gw57ecsSwWIpgG2MphVv19LPxLZ5M42zDZRPAQKb9nM
	K63ny3y4q1JAoNQlCMlbT4+VNig=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Native build fails in winsup/cygwin/libc/strptime.cc because of strtou?l_l()
To: cygwin@cygwin.com
References: <930c2619-1e9e-7275-c245-0a8c4bd92e6c@t-online.de> <20160824082813.GB1493@calimero.vinschen.de>
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker@t-online.de>
Message-ID: <929a5346-a4e1-99f0-fe63-5c1bca7cdd30@t-online.de>
Date: Wed, 24 Aug 2016 20:20:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160824082813.GB1493@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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