X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=S6
	DMpc7ZYRNcYi0ijQgOGgJO7Fa8F3ExnxwcNx1tisg040tV3eSciGMFqS0kbnTEdQ
	nNPtOd/iyfEF5ArO9nVOce6IrI7EIbm4TnnyBDe833WswRNoWeQ+KvnGu7pM3+dQ
	ZnTq2qM6DD42VnZYh2DB0oAgomALMzRncVXCPYQkM=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=EkNWdM3B
	XeHhDNe97M8ulwLeHTg=; b=BjiO95e26OSH3QFMwt4d9dXeMy5TGNQknRReojTJ
	LDBnQAiwJnH41AZhV8T6anoowVoD95W/AnDEkHk7YUr0vA0+91icSM9epmkmriYV
	/edOkMwtWaUCFacP4Dy9PmiCL3CSJ7nMJn8RzPimOoltn2cf7Ic+/30dvV0/8C5t
	6s8=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=
X-HELO:	mail-vk0-f46.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to; bh=uIWPfd9FJc4aVUKBCLGyh1l+hq7J6VsmRuFGZKeyWj8=; b=Uo/IoN4ObpfrhZ7iNiHEePASZ6r/RHoFxDtHRdtjSS5/8QruqGRo7IobMvJvidiB41 eTb/3NUxEUBvKbimrE8T3YG6i3Hi1l0q5YxOrgrLIGTxzHfc4Hbon80YYptbQ8T4GJfb SGxjHEQyoLbbEgic+D90Wa8F1nIri1NHOYyjBcgPOt4/Mr25VuszJfNBHiReFfkUNdGH LI7kF5XsgdNvTYVE+u5LEopy1sIqD3KBGCAEROJg2mWZI20e+ymQob+JNxUI+cz/zJQH Uv8Ru48yUSXo7AfZp1pswaLjNMDSKg+mVQTNAW0JhhXsp+bcfhA23ZCVuHUFeCT+aSCG m6mA==
X-Gm-Message-State:	AOPr4FXWWQ7Z5916wdM+fCznPrkNOEhnujXizfktM0D7z6ram3/dEiZ+lbzWgFRuziFT1OILRrBuPuRa4XMmkg==
MIME-Version:	1.0
X-Received:	by 10.176.1.173 with SMTP id 42mr11950514ual.76.1460750168312; Fri, 15 Apr 2016 12:56:08 -0700 (PDT)
In-Reply-To:	<20160415192350.GD24565@calimero.vinschen.de>
References:	<CAAkR8+sqWOntu_zZ3K_CvkVA5mjnJEM1N=GN1SzK-oFvJ3BxsA AT mail DOT gmail DOT com> <20160415192350 DOT GD24565 AT calimero DOT vinschen DOT de>
Date:	Fri, 15 Apr 2016 12:56:08 -0700
Message-ID:	<CAAkR8+uhSv8EPFJyYgt48H05O+uFqfTaVG+Fv0UH74OYinYWkQ@mail.gmail.com>
Subject:	Re: Cygwin 64bits gcc produces erroneous constants with the win32 headers.
From:	Nicolas Noble <pixel AT nobis-crew DOT org>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

On Fri, Apr 15, 2016 at 12:23 PM, Corinna Vinschen
<corinna-cygwin AT cygwin DOT com> wrote:
> On Apr 15 12:05, Nicolas Noble wrote:
>> I originally entered a bug on msys2's bug tracker, but it turns out
>> they only repackage cygwin packages, and I have verified this is an
>> issue on cygwin too, so I am now sending that report here.
>>
>> Original entry:
>>
>> https://github.com/Alexpux/MSYS2-packages/issues/555
>>
>>
>>
>> Basically, the 64 bits "gcc-core" and "w32api-headers" cygwin packages
>> aren't really compatible with each others.
>
> They are not supposed to.  You have to make sure to separate the
> win32 and Cygwin headers carefully.

I'm not sure I am getting that reply. The gcc-core package is only a
compiler, and I am talking about the "gcc" binary contained within.
The example I am showing is technically using only the w32api-headers,
trying to use the win32 api as described here:
https://cygwin.com/faq-nochunks.html#faq.programming.win32-api

>
>> As far as I understand,
>> this isn't an issue already documented here:
>> https://cygwin.com/faq-nochunks.html#faq.programming.win32-api
>
> It's documented in https://cygwin.com/faq.html#faq.programming.64bitporting

Right, but that isn't the same thing. I am well aware of the various
issues tied with sizeof(long), otherwise it would have taken me a lot
more time to understand what was going on here. I am talking about the
fact that the cygwin-provided w32api-headers package doesn't properly
work with the cygwin-provided 64 bits gcc. Unless I am mistaken
somewhere, this isn't an issue with the example code. This is an issue
when trying to compile a 64 bits binary that uses the win32 api,
nothing more.

--
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

- Raw text -