X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 9 Oct 2008 10:10:38 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: __CYGWIN_USE_BIG_TYPES__
Message-ID:	<20081009141037.GE13923@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<001901c929f3$030ee7b0$4001a8c0 AT mycomputer> <042101c929fb$1a61d8c0$9601a8c0 AT CAM DOT ARTIMI DOT COM> <011201c92a05$531a5ed0$4001a8c0 AT mycomputer> <48EDF178 DOT 1020705 AT byu DOT net> <001801c92a08$3a074630$4001a8c0 AT mycomputer>
MIME-Version:	1.0
In-Reply-To:	<001801c92a08$3a074630$4001a8c0@mycomputer>
User-Agent:	Mutt/1.5.16 (2007-06-09)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Thu, Oct 09, 2008 at 01:11:57PM +0100, John Emmas wrote:
> ----- Original Message ----- From: "Eric Blake"
> Subject: Re: __CYGWIN_USE_BIG_TYPES__
>>
>> Please show us a reproducible test case (ie. self-contained C file with
>> cruft removed that triggered the message, and not just the one-line
>> snippet of the error message).  If it is something that compiles on Linux
>> but fails to compile on Cygwin, and you didn't use private headers, then
>> we will probably try to patch the cygwin headers to fix things.
>>
> Thanks Eric.  It'll take me some time because this is a big project (not
> written by me) so I'll need to cut it down as much as possible.  The 
> project
> does build correctly under Linux though - and I'm not using private headers
> (or any other code that isn't part of the original project).
>
> Might take me a week or so to narrow it down though.

"gcc -dDI -E" is probably your friend to help you track down who is including
what.

cgf

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

- Raw text -