From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: stub.h & stub.exe Date: 3 Jul 2003 11:56:41 GMT Organization: Aachen University of Technology (RWTH) Lines: 31 Message-ID: References: NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1057233401 28290 137.226.32.75 (3 Jul 2003 11:56:41 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 3 Jul 2003 11:56:41 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eric Wajnberg wrote: > : If you add "-v" to gcc's command line you will see them being > : generated. > Ok, but I am not using "-v" to compile my code. A misunderstanding. Martin wanted to suggest that you *should* try it with -v once in a while, to see what exactly happens during your compilation. -v is a debugging aid, using it might help you see through problems like this. > : They should normally automatically be removed. Which versions of GCC > : and DJGPP (include the date on libc.a too) are you using? > I do not know exactly where I can see what version I'm using. By using that '-v' flag, among other ways. The version of binutils may be important for this, too. What does ld -v print? And/or what do you get if you type dir c:\djgpp\manifest (change pathname of DJGPP installation director if it's not c:\djgpp) -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.