X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 9 Oct 2008 12:14:28 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: __CYGWIN_USE_BIG_TYPES__ Message-ID: <20081009161428.GI13923@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> <48EDF3DF DOT 9090000 AT byu DOT net> <003401c92a1d$44ad5c40$4001a8c0 AT mycomputer> <046201c92a21$eac47240$9601a8c0 AT CAM DOT ARTIMI DOT COM> <002801c92a27$8d6557d0$4001a8c0 AT mycomputer> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002801c92a27$8d6557d0$4001a8c0@mycomputer> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 04:56:11PM +0100, John Emmas wrote: >On Thu, Oct 09, 2008 at 04:15:51PM +0100, Dave Korn wrote: >>John Emmas wrote on 09 October 2008 15:43: >> >>> Create an empty CPP source file and simply add the following line:- >>> >>> #include >>> >>> 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..! >> >> Use "gcc" to compile C files and "g++" to compile C++ files. >> >>> If you can't reproduce this, then the most likely cause is that >> >>... you forgot to show us the compiler command-line you're using. >> >>/tmp $ cat f.cpp >> >>#include >> >>int main (int argc, const char **argv) >>{ >> return 0; >>} >>/tmp $ g++ f.cpp -o f >>/tmp $ echo $? >>0 >>/tmp $ >> >Sorry, I realised almost as soon as I'd posted. Here's what gets sent >to g++ (I've split all the elements onto different line just to improve >legibility). Is this enough Dave? > > g++.exe -Wall -g > -IF:/test/libs/vamp-sdk/ > -IC:/cygwin/usr/include/mingw > -IC:/cygwin/lib/gcc/i686-pc-cygwin/3.4.4/include/c++ > -IC:/cygwin/include > -IC:/cygwin/usr/include/gtk-2.0 > -IC:/cygwin/usr/include/glib-2.0 > -IC:/cygwin/usr/include/pango-1.0 > -IC:/cygwin/lib/glib-2.0/include > -IC:/cygwin/lib/gtk-2.0/include > -IC:/cygwin/usr/include/atk-1.0 > -IF:/test/libs/vamp-sdk/vamp-sdk/hostext > -c F:/test/libs/vamp-sdk/vamp-sdk/hostext/test.cpp > -o obj/Debug/vamp-sdk/hostext/test.o > >If that's not what you wanted, I'll do what you suggested, although I >don't really understand all the $ and echo stuff (vauguely remember it >from my DOS days). Are they commands that I need to type in? "DOS days"? Cygwin is intended to emulate a UNIX environment. $? is the exit status of a process. If it is zero it means the process completed successfully. 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/