🚀 go-pugleaf

mctupper@holly.colostate.edu (Xylen):
> I know it is a simple little thing, but I can't find it anywhere.
> 
> I want to include lines like :
> 
> #include <fstream.h>
> fstream myin;
> 
> myin.open("data");
> 
> myin >> x;
> 
> I think I need fstream.h and probally iostream.h, but I can't find them.
> I suppose they are part of a shared library somewhere, but I don't know

Are you compiling this with g++?  If so, check to make sure you have egcs-g++
installed (rpm -qa | grep egcs).

-- 
Mike Grandin

Mike wrote:
> Are you compiling this with g++?  If so, check to make sure you have egcs-g++
> installed (rpm -qa | grep egcs).


Yep, it works just fine with g++. I keep forgetting that I have three
different compilers. cc, gcc, and g++. What is the difference in them
anyway?  Besides different error messages.

Xylen
-- 
  __^__                                __^__ 
 ( ___ )------------------------------( ___ ) 
  | / | This message has been brought  | \ | 
  | / | to you by the language C and   | \ | 
  |___| the number F                   |___| 
 (_____)------------------------------(_____)

mctupper@holly.colostate.edu (Xylen):
> Yep, it works just fine with g++. I keep forgetting that I have three
> different compilers. cc, gcc, and g++. What is the difference in them
> anyway?  Besides different error messages.

I believe cc (c compiler) is what generally comes on a Unix box.  With linux,
cc is just a symlink to gcc (GNU c compiler).  Use g++ when you want to compile
anything c++ish.  From the man page, 'g++ is a script to call gcc with options
to recognize C++' So, when it comes down to it, they are really all the same
thing on linux.  

-- 
Mike Grandin

Mike <mike@www.intrig.com> wrote:
: mctupper@holly.colostate.edu (Xylen):
:> Yep, it works just fine with g++. I keep forgetting that I have three
:> different compilers. cc, gcc, and g++. What is the difference in them
:> anyway?  Besides different error messages.

: I believe cc (c compiler) is what generally comes on a Unix box.  With linux,
: cc is just a symlink to gcc (GNU c compiler).  Use g++ when you want to compile
: anything c++ish.  From the man page, 'g++ is a script to call gcc with options
: to recognize C++' So, when it comes down to it, they are really all the same
: thing on linux.  

Except I think on some machines, cc == gcc, and g++ == egcs.  Its all a
vicious conspiracy.  Suffice to say, in the Bad Old Days (tm) cc was
a symlink to gcc, and g++ was a symlink to gcc.  Gcc would act a little
differently depending on what you called it.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Michael J. Dwyer                      I doubt, therefore I might be.
mdwyer@holly.ColoState.edu       http://WWW.CS.ColoState.EDU/~dwyer/
Computer Science Major                      Amateur Radio Tech N0ZAP

mdwyer@holly.ColoState.EDU (Michael Dwyer):
> : I believe cc (c compiler) is what generally comes on a Unix box.  With linux,
> : cc is just a symlink to gcc (GNU c compiler).  Use g++ when you want to compile
> : anything c++ish.  From the man page, 'g++ is a script to call gcc with options
> : to recognize C++' So, when it comes down to it, they are really all the same
> : thing on linux.  
> 
> Except I think on some machines, cc == gcc, and g++ == egcs.  Its all a
> vicious conspiracy.  Suffice to say, in the Bad Old Days (tm) cc was
> a symlink to gcc, and g++ was a symlink to gcc.  Gcc would act a little
> differently depending on what you called it.
> 

Good call, on my system g++ isn't a script.  The man page must need to be
updated.  I wonder why the move was made from gcc to egcs.  Are gcc packages
still being developed, or did they just rename it to egcs?

 [Tue, 1:32pm]  ~  # rpm -qf /usr/bin/gcc /usr/bin/cc /usr/bin/g++
egcs-1.1.2-12
egcs-1.1.2-12
egcs-c++-1.1.2-12
 [Tue, 1:32pm]  ~  # ls -l /usr/bin/gcc /usr/bin/cc /usr/bin/g++
lrwxrwxrwx   1 root     root            3 Jan  8  1999 /usr/bin/cc -> gcc
-rwxr-xr-x   2 root     root        66188 Mar 21  1999 /usr/bin/g++
-rwxr-xr-x   3 root     root        64796 Mar 21  1999 /usr/bin/gcc

--
Mike Grandin

In article <slrn89eh3a.236.mike@localhost.localdomain>, mike@www.intrig.com (Mike) wrote:
> mdwyer@holly.ColoState.EDU (Michael Dwyer):
>> : I believe cc (c compiler) is what generally comes on a Unix box.  With linux,
>> : cc is just a symlink to gcc (GNU c compiler).  Use g++ when you want to compile
>> : anything c++ish.  From the man page, 'g++ is a script to call gcc with options
>> : to recognize C++' So, when it comes down to it, they are really all the same
>> : thing on linux.  
>> 
>> Except I think on some machines, cc == gcc, and g++ == egcs.  Its all a
>> vicious conspiracy.  Suffice to say, in the Bad Old Days (tm) cc was
>> a symlink to gcc, and g++ was a symlink to gcc.  Gcc would act a little
>> differently depending on what you called it.
> 
> Good call, on my system g++ isn't a script.  The man page must need to be
> updated.  I wonder why the move was made from gcc to egcs.  Are gcc packages
> still being developed, or did they just rename it to egcs?

Hi; just happened to see this while testing out a newsreader.

The "cc" program should always exist on a unix system (assuming there is a C compiler of some sort).  It is often just a link to the system's preferred compiler.  Same goes for "CC", except this will compile as C++ instead of C.  Some also have "c++", but "CC" is more standard.

With gnu systems, gcc is the C compiler and g++ is the C++ compiler.  Because gcc supports both C and C++ (both natively -- it doesn't need to translate C++ -> C like some compilers do), the same executable can compile both languages.  It probably checks its name (argv[0]) to see which language it defaults to.  Other programs do this, such as gzip -- it figures out whether to compress/decompress and where to send the data based on what its executable is called (gzip, gunzip, gzcat, etc).

EGCS is simply the Cygnus version of gcc/g++.  They had made their own branch in order to speed up development.  If you remember, gcc was stuck at V2.7.2 for quite a long time, until Cygnus started egcs.  Then some of the changes were merged back in to create gcc 2.8.0.  Eventually, the FSF decided that gcc would be better off if it was maintained officially by Cygnus, and they handed over the name.  So, now egcs and gcc are the same thing, and the current version is 2.95.

Just FYI.  :)

 _  _ _  _ ___ ___  ---"I don't get even - I just get odder."---
( \/ ( \/ (__ (__ ) |     Scott Scriven (Toy Keeper / XYZZ)    |
 \  / \  /  //  //  |       mailto:toykeeper@cheerful.com      |
 /  \ / /  //_ //_  |     irc:serdevian.dyn.omnipotent.net     |
(_/\_(_/  (___(___) |  http://www.vis.colostate.edu/~scriven/  |