Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning:	eos.vss.fsi.com: ford owned process doing -bs
Date:	Fri, 31 Oct 2003 15:38:50 -0600 (CST)
From:	Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender:	ford AT eos
To:	y2bismil AT engmail DOT uwaterloo DOT ca
cc:	cygwin AT cygwin DOT com
Subject:	Re: gcc and iostream - resolved
In-Reply-To:	<1067634448.3fa2cf107ba2a@www.nexusmail.uwaterloo.ca>
Message-ID:	<Pine.GSO.4.56.0310311536120.9896@eos>
References:	<1067549281 DOT 3fa18261b9137 AT www DOT nexusmail DOT uwaterloo DOT ca>
	<133687559107 DOT 20031031100848 AT familiehaase DOT de> <1067616628 DOT 3fa2897461121 AT www DOT nexusmail DOT uwaterloo DOT ca>
	<1067617166 DOT 3fa28b8ecc072 AT www DOT nexusmail DOT uwaterloo DOT ca>
	<1067622375 DOT 3fa29fe7e6898 AT www DOT nexusmail DOT uwaterloo DOT ca> <Pine DOT GSO DOT 4 DOT 56 DOT 0310311303170 DOT 9896 AT eos>
	<1067629896 DOT 3fa2bd48db2e8 AT www DOT nexusmail DOT uwaterloo DOT ca>
	<1067634448 DOT 3fa2cf107ba2a AT www DOT nexusmail DOT uwaterloo DOT ca>
MIME-Version:	1.0

On Fri, 31 Oct 2003 y2bismil AT engmail DOT uwaterloo DOT 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/

- Raw text -