Mail Archives: djgpp/2000/08/11/09:30:24
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.
- Raw text -