#include <stdio.h> problem

dmalsbury · 01-23-2004, 08:38 PM

slackware 9.1 - every time i use

#include <stdio.h>

as the 1st line of my code, I get a page full of errors when I compile with cc, removing it works ok, with no errors.

I thought I needed it. can you help?

newbie Doug Malsbury

h/w · 01-23-2004, 08:42 PM

dmalsbury · 01-23-2004, 08:54 PM

should i use cc or gcc or gpp? dont know if that will change my problem though.

h/w · 01-23-2004, 09:02 PM

see if you get that error with gcc (im thinking you will...)

dmalsbury · 01-23-2004, 09:13 PM

i do.
whats the diff btwn cc, gcc, etc?
why does it seem to work w/o the #include?

thanx for your help
Doug

h/w · 01-23-2004, 09:20 PM

i'm not sure about this, as i havent come across errors with headers in C. can you post the errors that fly by?

also, is it only with stdio.h or any header file?

zekko · 01-24-2004, 12:20 AM

Post the errors and maybe the code (if its not too big), I'm sure someone here can help you out.

UltimaGuy · 01-24-2004, 01:16 AM

The 'cc' is the C++ precompiler and using it for C code is bound to cause errors. Try using gcc, and then post the errors here....

cjcuk · 01-24-2004, 10:37 AM

Quote:

Originally posted by UltimaGuy
The 'cc' is the C++ precompiler and using it for C code is bound to cause errors. Try using gcc, and then post the errors here....

It should not be, you obviously have a strange system setup. `cc' is supposed to be a C Compiler or a symbolic link to the preferred C Compiler for the system. More often than not, `cc' will be a symlink to `gcc'.

amos · 01-24-2004, 11:28 AM

If you're compiling a c++ program use: #include <stdio>
but follow it with: using namespace std;
or lots of errors occur.
You can still use #include <stdio.h> and you'll get a warning that its deprecated but everything should work without the need to resort to 'using namespace std;'.

If you're compiling a c++ program invoke the compiler with: g++ myprog.cpp (possibly adding -omyprog, to get an executable called myprog).

'gcc' calls the c compiler part of gcc, 'g++' calls the c++ compiler part.

Cheers
Amos

MartinN · 01-24-2004, 01:22 PM

Quote:

Originally posted by amos
If you're compiling a c++ program use: #include <stdio>
but follow it with: using namespace std;
or lots of errors occur.
You can still use #include <stdio.h> and you'll get a warning that its deprecated but everything should work without the need to resort to 'using namespace std;'.

If you're compiling a c++ program invoke the compiler with: g++ myprog.cpp (possibly adding -omyprog, to get an executable called myprog).

'gcc' calls the c compiler part of gcc, 'g++' calls the c++ compiler part.

Cheers
Amos

It's cstdio, not stdio.

Martin

amos · 01-24-2004, 04:49 PM

My mistake.

Cheers
Amos

UltimaGuy · 01-25-2004, 01:24 AM

cjcuk, I am not at my system, so I can't check out. But I am pretty sure that in my RH9 box, the 'cc' command on any cpp source file just precompiles it. I've even read something about compilers and know a few flags that I regularly use in my make files. And so I think that 'cc <progname.cpp>' in my box just precompiles the source file and outputs to the console.

kev82 · 01-25-2004, 08:55 AM

cc should definatly be the preferred C compiler for the system

by the latest Linux From Scratch book
Many packages use the name cc to call the C compiler. To satisfy those packages, create a symlink:

ln -s gcc /usr/bin/cc

the (GNU)C preprocessor is cpp and tends to live in /usr/bin or /usr/lib

UltimaGuy · 01-25-2004, 09:05 AM

Oh, sorry guys. I had created a link to cpp as cc, and I use it quite regularly, so I was confused a bit. I back off with humble apologies....