Re: gcc and iostream - final issue

2003-10-31 Thread y2bismil
Okay all, I think I've narrowed down the issue to a conflict with mingw. This is mingw installed via cygwin setup not the stand alone version. In general then, anyone know what the exact issues are regarding mingw and cygwin. I've googled, and come across a few things. I've tried the option

Re: gcc and iostream - final issue

2003-10-31 Thread Christopher Faylor
On Fri, Oct 31, 2003 at 12:46:15PM -0500, [EMAIL PROTECTED] wrote: I think I've narrowed down the issue to a conflict with mingw. This is mingw installed via cygwin setup not the stand alone version. Anyone have any ideas on what params/path to pass to g++ on both compiling and linking stages?

Re: gcc and iostream - final issue

2003-10-31 Thread Brian Ford
On Fri, 31 Oct 2003 [EMAIL PROTECTED] wrote: Okay all, I think I've narrowed down the issue to a conflict with mingw. This is mingw installed via cygwin setup not the stand alone version. Could you please repost your exact command line and the resulting output after following the suggestion

Re: gcc and iostream - final issue

2003-10-31 Thread y2bismil
Hi Brian, I did try all the items mentioned, and none have helped so far. The error states that I can get it into are: 1. use full std:: qualifier in which case it cries at compile time about cout not being in namespace std 2. It complains at link time that cout is an undefined reference.

Re: gcc and iostream - final issue

2003-10-31 Thread Brian Ford
On Fri, 31 Oct 2003 [EMAIL PROTECTED] wrote: 1. Putting libraries at the end has not helped You must always do this. This is the way linkers work. 2. I'm using g++ only now in both compile and link stages...Just out of curiousity though, isn't gcc supposed to 'call' g++ internally based