On Fri, 31 Oct 2003 [EMAIL PROTECTED] 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'
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 base
Hi all,
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.
2. Only included SysHdrPath +=C:/cygwin/usr/include/mingw as the system path
3.
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. St
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 sugges
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 stage
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
-n
Ah, okay,
running just the preprocessor on the file, This is what I get:
Nothing weird is being pulled in from other directories. The iostream
references are as follows:
# 1 "/usr/include/c++/3.3.1/iostream" 1 3
# 43 "/usr/include/c++/3.3.1/iostream" 3
..
# 1 "/usr/include/c++/3.3.1/backward/io
Hi all,
Okay, I've replaced the using namespace std with std:: for each call to
cout/cin. The error I got was interesting. It seems cout is not declared in
namepace std.
error: `cout' undeclared in namespace `std'
Obviously something is up. If anyone can think of anything, let me know. The
o
Hallo y2bismil,
Am Donnerstag, 30. Oktober 2003 um 22:28 schriebst du:
> I'm having a linking problem with GCC and iostream. I'm not sure if it has
> anything to do with cygwin, so I'll check here.
> I am using
> #include
> using namespace std;
> Its a pretty large project. First, all the s
> > I am using
> > #include
> > using namespace std;
> >
> I might reverse the order of those two, but I don't know if it matters.
> I'm not a c++ person.
>
No, he's got that right. Putting the "using" cart before the "#include"ed horse
could conceivably cause problems.
--
Gary R. Van Sickle
I don't know if any of these will address your problem, but...
On Thu, 30 Oct 2003 [EMAIL PROTECTED] wrote:
> I am using
> #include
> using namespace std;
>
I might reverse the order of those two, but I don't know if it matters.
I'm not a c++ person.
> Its a pretty large project. First, all th
possibly out-dated gcc code? check your namespaces?
: undefined reference to `ostream::operator<<(char const*)
: undefined reference to `_cin'
: undefined reference to `_cout'
:undefined reference to `istream& operator>>(istream&, smanip const&)'
Tim Prince
--
Unsubscribe info: http://cy
13 matches
Mail list logo
