On Wed, Sep 13, 2000 at 07:48:41AM -0500, Steve Fox wrote:
[drfickle@potato remotehost_applet-0.2.0]$ ll `which gcc`
lrwxrwxrwx1 root root 17 Aug 25 17:12 /usr/bin/gcc -
/usr/bin/colorgcc*
-- [drfickle@potato remotehost_applet-0.2.0]$ ll /usr/bin/g++
lrwxrwxrwx1 root
Antony Suter wrote:
--
- Antony Suter ([EMAIL PROTECTED]) "Examiner" openpgp:71ADFC87
- "And how do you store the nuclear equivalent of the universal solvent?"
Easy, the universal solvent is a binary
Julian
Yo,
like
include header
rather than
include header.h
?
It must work with some versions of gcc as other people can compile it.
Just curious but you use gcc command to compile c++ app? I would tend to use
the g++ command if I were you.
It's the same
Geoffrey Lee wrote:
It's the same thing. gcc detects that you're doing c++ based on file
extension I believe
Uhh, kind of.
Say ...
-- cut --
#include iostream
int main () {
cout "Hello world" endl;
return 0;
}
--/cut --
When you use g++ it will work
Yo,
[drfickle@potato remotehost_applet-0.2.0]$ ll `which gcc`
lrwxrwxrwx1 root root 17 Aug 25 17:12 /usr/bin/gcc -
/usr/bin/colorgcc*
-- [drfickle@potato remotehost_applet-0.2.0]$ ll /usr/bin/g++
lrwxrwxrwx1 root root 17 Aug 25 17:12 /usr/bin/g++ -
Steve Fox [EMAIL PROTECTED] writes:
Does anyone know why gcc b0rks when someone includes things in a C++ app
like
include header
rather than
include header.h
?
It must work with some versions of gcc as other people can compile it.
titi said: it's just two different include
Yo,
Does anyone know why gcc b0rks when someone includes things in a C++ app
like
include header
rather than
include header.h
?
It must work with some versions of gcc as other people can compile it.
Just curious but you use gcc command to compile c++ app? I would tend to use
Geoffrey Lee wrote:
Yo,
Does anyone know why gcc b0rks when someone includes things in a C++ app
like
include header
rather than
include header.h
?
It must work with some versions of gcc as other people can compile it.
Just curious but you use gcc command to
