X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-Trace:	90027004/mk-filter-1.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/79.66.94.76/None/johne53 AT tiscali DOT co DOT uk
X-SBRS:	None
X-RemoteIP:	79.66.94.76
X-IP-MAIL-FROM:	johne53 AT tiscali DOT co DOT uk
X-MUA:	Microsoft Outlook Express 6.00.2900.2180Produced By Microsoft MimeOLE V6.00.2900.2180
X-IP-BHB:	Once
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	ApsEAJ+07UhPQl5M/2dsb2JhbACEYrpOgWo
X-IronPort-AV:	E=Sophos;i="4.33,383,1220223600"; d="scan'208";a="90027004"
Message-ID:	<003401c92a1d$44ad5c40$4001a8c0@mycomputer>
From:	"John Emmas" <johne53 AT tiscali DOT co DOT uk>
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> <48EDF3DF DOT 9090000 AT byu DOT net>
Subject:	Re: __CYGWIN_USE_BIG_TYPES__
Date:	Thu, 9 Oct 2008 15:42:31 +0100
MIME-Version:	1.0
X-Mailer:	Microsoft Outlook Express 6.00.2900.2180
X-IsSubscribed:	yes
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

----- 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
>
> That reads poorly.  I meant:
>
> a self-contained C file that triggers the message and with as much cruft
> unrelated to the message removed
>
Hi Eric,

This has turned out to be blindingly simple to reproduce - though not
blindingly obvious (at least not to me!)

Create an empty CPP source file and simply add the following line:-

#include <fstream>

Now try to compile the file.  In my case I get around 50 errors, the first
of which is:-

\usr\include\pthread.h:  77: error: `pthread_attr_t' was not declared in
this scope

Now change the file's extension to ".c" and re-compile.  This gives another
host of errors, but different errors from the previous ones..!

One important difference between Linux and Cygwin is that my Linux partition
has just one file called fstream which is in  /usr/include/c++/4.1.2
Cygwin has 3 copies, including one that's part of 'boost'.  It's unlikely
that the boost version is getting included by accident because it isn't in
my compiler's search paths.

If you can't reproduce this, then the most likely cause is that some other
header files also have multiple versions and I need to re-order my search
paths.  However, I'd be grateful if you can try this when you get some spare
time.

Thanks,

John 


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