From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Linker warning
Date: 11 Aug 2000 13:15:57 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 30
Message-ID: <8n0uad$e1i$1@nets3.rz.RWTH-Aachen.DE>
References: <3992D37A DOT D0274FA6 AT ma DOT tum DOT de> <glq5pskesd9njjpdlja7mr1e8pp1q7nd1o AT 4ax DOT com> <3993A4C0 DOT D972C04D AT ma DOT tum DOT de>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 965999757 14386 137.226.32.75 (11 Aug 2000 13:15:57 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 11 Aug 2000 13:15:57 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Waldemar Schultz <schultz AT ma DOT tum DOT de> wrote:
> unfortunetaly the proj is huge, and that warning popped up from one minute to
> the other, after some minor changes in the sources, so I don't know wher to
> start boiling down.

If possible (i.e. you're using a version control system for that
project): start by backing out those 'minor changes', one by one, and
show us the context of the one that triggered the warning.

> shuodn't the COFF debug info be O.K. when I recompile everything?
> perhaps gcc or ld is broken. 

Hardly a possibility. It's almost impossible for them to start being
broken out of the blue, while still producing valid executables rather
than crashing themselves.

> #ifdef GLOBALS_G
>  #define vextern
> #else
>  #define vextern extern
> #endif

It may very well be that this preprocessor voodoo of yours is the
source of the problem. I think it'll be instructive to check that you
use it 100% correctly. Offhand, e.g., I'd suspect a typo in that
#ifdef: shouldn't it read GLOBALS_*C*, instead of GLOBALS_*G*?

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.