From: uhfgood AT aol DOT com (Uhfgood)
Newsgroups: comp.os.msdos.djgpp
Subject: -KWII-  Not a problem, but confusing, please help?
Lines: 30
NNTP-Posting-Host: ladder02.news.aol.com
X-Admin: news AT aol DOT com
Date: 20 Oct 1998 15:47:06 GMT
Organization: AOL http://www.aol.com
Message-ID: <19981020114706.11792.00003389@ng73.aol.com>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello DJGPP'ers.  I have another question.  NOTE: I *did* read the faq and the
docs...  This is not an urgent question, it's just something that's puzzling
me...
okay consider this command line:

gcc fnlcall.c -s -o fnlcall.o

What this generates (i'm sure all of you know) is fnlcall.o and fnlcall.exe
Now.  It was interesting to see that fnlcall.o was nearly the same size as
fnlcall.exe but to me it looked like the fnlcall.o was too big to be an object 
file.  I looked up in the docs the -c which tells it not to link...  and
produces
a *real* object file which is actually much smaller than the executable.
Well what's actually puzzling me is what did i create (that is with the com-
mand line above, what is actually being outputted, (I mean what is fnlcall.o 
since it's not a real object file)... I do find that fnlcall.o is different
than fnlcall
the executable...  okay lemme recap (just in case some of you don't under-
stand my question)...

when i use gcc fnlcall.c -s -o fnlcall.o, what is fnlcall.o seeing that it's
not a 
real object file?  what am I producing with the line above?  and why is it
different
then the executable?  Please reply, if you are still confused write me back and
i'll try to re-clarify the question, thank you.                          -KWII-

*Keith Weatherby II*
*Uhfgood AT aol DOT com*
*Vice AT gconn DOT com*