Thread: Error: Multiple definition of '_main'...

HI,
As u may think, I am new to C programing and as I was making programs in C, my first program was successfully compiled while all the programs that followed contained load of errors; the main being
<<Error: Multiple definition of '_main'>>
I think that the first program that was compiled has a 'main' that links with all the other programs that I want to create.
Can anyone tell me what is the way out for creating other programs without this error??
By the way, I am using DJGPP's C compiler on a win98 PC.
Is there something that I have to change the properties anywhere??
Any help appreciated.

As I am new to C programing, I dont know about the linking of the *.c files. What I mean to say is that first I made my first C program named 'HelloWorld.c' and next I wanted to make another C program relating to addition of 2 numbers <add.c>.
Now, HelloWorld.c runs perfectly without errors, but the other programs that I want to write, are not compiled properly and are with loads of errors that I don't think have any.
i.e. add.c when compiled says:::
Error: Multiple definition of '_main' with other errors following it.
When I point to this error, the DJGPP program takes me back to the 'main' statement I wrote in HelloWorld.c .

Well, this is specific to your compiler.

Evidently, DJGPP (which I've never used) thinks you're trying to compile "add.c" and "HelloWorld.c" together as one program, when you clearly want them to be separate programs.

If DJGPP is an IDE, make sure you clear everything and create a new project (or whatever appropriate).

Ok, I think I should try Turbo C to make my programs work.
Thanks a lot.

> Ok, I think I should try Turbo C to make my programs work.
1. this won't solve the problem of having two mains
2. it's a step back to the stone age.

You're going to have to call one of the functions something else, and call it from the single main() which remains.

I think I found the problem.
In my computer, DJGPP considers all the .c programs written one after the other are read as a single project that does not require the repetitive codes such as 'main'...
However, I do not know how to make single programs work as their own entity and not as a whole project.
So, now I am using Turbo C which does not have the same facility (/annoyance).
Thanks for your replies.
Anyways, for me as a beginner of C language, Turbo C is a CLASSIC compiler, though old/ outdated; it works for ME.
[B]Those who proclaim themselves to be the God of C are often imperfect themselves. I hope you don't mind this and agree...
GOD BLESS ALL... :-)

I doubt that turbo c doesn't have the option of compiling/linking multiple files.

Originally Posted by thunderdome

I think I found the problem.
In my computer, DJGPP considers all the .c programs written one after the other are read as a single project that does not require the repetitive codes such as 'main'...
However, I do not know how to make single programs work as their own entity and not as a whole project.

I think it would be better for you to learn your tools rather than change them at the first bit of confusion. This just doesn't seem an auspicious start to your coding efforts. Can't you just look under "File" for "New Project" or something like that? It's probably that simple.

So, now I am using Turbo C which does not have the same facility (/annoyance).
Thanks for your replies.
Anyways, for me as a beginner of C language, Turbo C is a CLASSIC compiler, though old/ outdated; it works for ME.

I think "classic" is too generous a term -- the last release of Turbo C was over 15 years ago, wasn't it? You don't need a fancy ide (I use gvim and an xterm myself) but you really should learn C with a modern compiler.

Originally Posted by thunderdome

I think I found the problem.
In my computer, DJGPP considers all the .c programs written one after the other are read as a single project that does not require the repetitive codes such as 'main'...
However, I do not know how to make single programs work as their own entity and not as a whole project.
So, now I am using Turbo C which does not have the same facility (/annoyance).
Thanks for your replies.
Anyways, for me as a beginner of C language, Turbo C is a CLASSIC compiler, though old/ outdated; it works for ME.
[B]Those who proclaim themselves to be the God of C are often imperfect themselves. I hope you don't mind this and agree...
GOD BLESS ALL... :-)

"Classic" is nice if you're talking cars, movies, and perhaps television programs.

It's NOT nice if you're talking compilers. A compiler that has not had a release in 15 years may not support certain things, and may allow you to do heinous things in your code, that a good, up-to-date compiler will catch.

The compiler is telling you things for a reason. While it is annoying, even maddening, at times, if you dig down and find out WHY the compiler is gakking on you, and what you need to do to fix it, you'll become a better programmer.

As for Salem, from the posts I've read, he's perfectly capable of calling himself God of the C..... while it's probably tongue in cheek, he certainly knows his stuff.....

So -- pull out your original compiler, get your favorite beverage, and sit down and dig in!

Thanks all.
Sorry To Salem If He Did Mind What I Said. I think I was rude in saying it so badly.

Can anyone tell me if there is any compiler which can give us the time to look at the output rather than typing getch(); OR other methods like printf(); ? Its b'coz the book that I refer doesn't have getch(); in any of its programs. So I think there must be such a compiler.

BTW, I am using Win98 and have now tried both gvim and Borland. (gvim seems to be rather hard to use for me !) Yes, the Borland version is good.

You ever heard of a help file?

Originally Posted by Bubba

You ever heard of a help file?

Or was we sometimes mutter in the office: "RTFM"


I'm going to take a stab at what thunderdome is getting at. To me it sounds like he needs/wants/would like a debugger. The ability to step through the code as it executes.

If you're running the code in "real time", and want to see what is going on, you do need to use print statements (printf to stdout, fprintf to a trace file etc). There's no compiler functionality that will do that for you.

It might be a part of your IDE, but I'm not all that familiar with IDEs on Windows (although I might have to become more familiar in the near future).