g++ problem

I am having problems with g++.
I have a simple script:

Code:

#include <iostream.h>
#include <stdlib.h>
using namespace std;
int main()

{

	int x = 5;
	cout << "test" << endl;
        cout <<  x << endl;



}

and I compile it ( g++ Desktop/test.cpp -o run )

I get a error:

Code:

In file included from /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c++/4.1.2/backward/iostream.h:31,
                 from Desktop/test.cpp:1:
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c++/4.1.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.

and then this error when I run the script ( g++ run )

Code:

In file included from /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c++/4.1.2/backward/iostream.h:31,
                 from Desktop/test.cpp:1:
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c++/4.1.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
[root@localhost ~]# g++ go
go: In function `_start':
(.text+0x0): multiple definition of `_start'
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crt1.o:(.text+0x0): first defined here
go:(.rodata+0x0): multiple definition of `_fp_hw'
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crt1.o:(.rodata+0x0): first defined here
go: In function `_fini':
(.fini+0x0): multiple definition of `_fini'
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crti.o:(.fini+0x0): first defined here
go:(.rodata+0x4): multiple definition of `_IO_stdin_used'
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crt1.o:(.rodata.cst4+0x0): first defined here
go: In function `__data_start':
(.data+0x0): multiple definition of `__data_start'
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crt1.o:(.data+0x0): first defined here
go:(.rodata+0x8): multiple definition of `__dso_handle'
/usr/lib/gcc/i386-redhat-linux/4.1.2/crtbegin.o:(.rodata+0x0): first defined here
go: In function `_init':
(.init+0x0): multiple definition of `_init'
/usr/lib/gcc/i386-redhat-linux/4.1.2/../../../crti.o:(.init+0x0): first defined here
/usr/lib/gcc/i386-redhat-linux/4.1.2/crtend.o:(.dtors+0x0): multiple definition of `__DTOR_END__'
go:(.dtors+0x4): first defined here
/usr/bin/ld: warning: Cannot create .eh_frame_hdr section, --eh-frame-hdr ignored.
collect2: ld returned 1 exit status

I did change the iostream.h into iostream and stdlib.h into stdlib, but same thing.

So what is causing all these errors, and how can I fix it ?

I am running Fedora Core 7 on VMware

You don't type g++ to run it as well.

It's
g++ -o prog prog.cpp
to compile it,

then
./prog
to run it

That's it.

Thanks !

Maybee any other usefull tips for g++ for someone coming from programing on windows ?

Advice for people moving from Windows -> *nix? If you're not used to it already, get used to using a terminal window.

Actually, I would recommend that for Windows users, too.....

stdlib.h into stdlib

<cstdlib>
The headers inherited from C have a c prefix in their extension-less names.

Originally Posted by CornedBee

<cstdlib>
The headers inherited from C have a c prefix in their extension-less names.

Likewise for

Code:

#include <iostream.h>

should be

Code:

#include <iostream>

--
Mats

u can also use the header

Code:

#include <iostream.h>

without,

Code:

using namespace std;

the interesting way out is name the file with extension .C
mark it, its CAPS "C".

Hence u can compile that using g++ compiler as discussed b4...

when u compile the code as

Code:

g++ -o prog prog.C

there would be some warning messages...so hence disable the warning by using this piece of option along with the g++ command

Code:

g++ -o prog prog.C -Wno-deprecated

and finally,

Code:

./prog

I hope this will give u a very clear picture...

But why would you want to write new code using deprecated features?

Building in obsolescence before you've even begun is no way to go.

I appreciate ur thinking...
BUT, there is nothing wrong in having knowledge of a bit more features supported by g++, in case the codes which are really obsolute but needs to be compiled in g++...hence g++ compiler has a good support for obsolute codes compilation too...

It's good to have knowledge that helps you understand outdated programs. BUT when imparting this knowledge, you should always point out that this knowledge is indeed only for understanding of old programs and not for using in new programs.

Oh, and don't use a capital C as a file ending for C++ programs, as this trick makes it unportable to systems where the filesystem is case-insensitive - like Windows.