Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Dave Korn" To: "'Hans Horn'" , Subject: RE: compilation with -mno-cygwin Date: Tue, 13 Apr 2004 17:15:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 13 Apr 2004 16:15:10.0593 (UTC) FILETIME=[7E863710:01C42172] > -----Original Message----- > From: cygwin-owner On Behalf Of Hans Horn > Sent: 13 April 2004 17:07 > > Has anybody got a clue what's going on? > > H. Nope, but you'd get a better idea if you try running g++ -E -mno-cygwin -ansi -DGCC3X -DLINUX -DINLINE=inline -fno-default-inline -W -Wno-deprecated -fomit-frame-pointer -ffast-math -mcpu=pentium4 -march=p entium4 -mfpmath=sse -O2 -I./ -o xyz.no-cyg.i xyz.cpp -v g++ -E -ansi -DGCC3X -DLINUX -DINLINE=inline -fno-default-inline -W -Wno-deprecated -fomit-frame-pointer -ffast-math -mcpu=pentium4 -march=p entium4 -mfpmath=sse -O2 -I./ -o xyz.cyg.i xyz.cpp -v at the command line. Then you'll be able to look through the preprocessed source files, and get a clearer idea why all those symbols are defined in the cygwin environment but not the mingw environment; you'll see exactly what files are including which ones in what order from the #line directives; and the output from the command lines (because of the '-v') will show you the different search paths etc. that are passed to the compiler in the two cases. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/