From: Brian Ford <ford@vss.fsi.com>
To: y2bismil@engmail.uwaterloo.ca
Cc: cygwin@cygwin.com
Subject: Re: gcc and iostream - resolved
Date: Fri, 31 Oct 2003 22:48:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0310311536120.9896@eos> (raw)
In-Reply-To: <1067634448.3fa2cf107ba2a@www.nexusmail.uwaterloo.ca>
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/
next prev parent reply other threads:[~2003-10-31 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 22:35 gcc and iostream y2bismil
2003-10-31 2:26 ` Brian Ford
2003-10-31 7:20 ` Gary R. Van Sickle
2003-10-31 10:00 ` Gerrit P. Haase
2003-10-31 16:22 ` y2bismil
2003-10-31 17:00 ` y2bismil
2003-10-31 18:13 ` gcc and iostream - final issue y2bismil
2003-10-31 18:39 ` Christopher Faylor
2003-10-31 21:07 ` Brian Ford
2003-10-31 21:34 ` y2bismil
2003-10-31 22:05 ` gcc and iostream - resolved y2bismil
2003-10-31 22:48 ` Brian Ford [this message]
2003-10-31 22:24 ` gcc and iostream - final issue Brian Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0310311536120.9896@eos \
--to=ford@vss.fsi.com \
--cc=cygwin@cygwin.com \
--cc=y2bismil@engmail.uwaterloo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).