From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6042 invoked by alias); 31 Oct 2003 21:38:51 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 6033 invoked from network); 31 Oct 2003 21:38:50 -0000 Received: from unknown (HELO esds.vss.fsi.com) (66.136.174.212) by sources.redhat.com with SMTP; 31 Oct 2003 21:38:50 -0000 Received: from eos.vss.fsi.com (eos [198.51.27.61]) by esds.vss.fsi.com (8.11.6+Sun/8.9.1) with ESMTP id h9VLcok25683; Fri, 31 Oct 2003 15:38:50 -0600 (CST) Received: from localhost (ford@localhost) by eos.vss.fsi.com (8.11.6+Sun/8.11.6) with ESMTP id h9VLcoG06568; Fri, 31 Oct 2003 15:38:50 -0600 (CST) X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Fri, 31 Oct 2003 22:48:00 -0000 From: Brian Ford X-X-Sender: ford@eos To: y2bismil@engmail.uwaterloo.ca cc: cygwin@cygwin.com Subject: Re: gcc and iostream - resolved In-Reply-To: <1067634448.3fa2cf107ba2a@www.nexusmail.uwaterloo.ca> Message-ID: References: <1067549281.3fa18261b9137@www.nexusmail.uwaterloo.ca> <133687559107.20031031100848@familiehaase.de> <1067616628.3fa2897461121@www.nexusmail.uwaterloo.ca> <1067617166.3fa28b8ecc072@www.nexusmail.uwaterloo.ca> <1067622375.3fa29fe7e6898@www.nexusmail.uwaterloo.ca> <1067629896.3fa2bd48db2e8@www.nexusmail.uwaterloo.ca> <1067634448.3fa2cf107ba2a@www.nexusmail.uwaterloo.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-10/txt/msg01872.txt.bz2 On Fri, 31 Oct 2003 y2bismil@engmail.uwaterloo.ca wrote: > I got it resolved by doing the following: > > 1. Used dos style names because (I don't think this was needed, but clearcase > paths...were not setup under the cygwin environment, so I just used the windows cmd. > Never feed DOS style paths to Cygwin's gcc/g++. > 2. Only included SysHdrPath +=C:/cygwin/usr/include/mingw as the > system path > Don't do that either. > 3. DID NOT USE -nostdinc++ in both compile/link > 4. used -mno-cygwin in both compile/link > 5. DID NOT USE -nodefaultlibs in link > All good. > 6. still linked with -lwsock32 -lstdc++ -lgcc, but I think only lwsock32 is > needed. But this is good enough for now. > Yes, only -lwsock32 is needed. > In short, I think I ended up messing myself over. > Yes! You're making this *way* too hard. Just use -mno-cygwin and comple away. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/