Mail Archives: djgpp/2000/01/18/15:44:49
On Mon, 17 Jan 2000, Gisle Vanem wrote:
> > Simply this was best I was able to do to get version automatically in
> > using definition in gcc specs.
>
> Why couldn't '__DJGPP__', '__DJGPP_MINOR__' etc. be put in the specs
> file? (updating 'specs' when a new djgpp version is released).
It was like that before v2.03. However, the specs file is specific to
the GCC version, and GCC ports are released with no particular
connection to DJGPP releases, and at a much higher rate. So v2.03
removed lib/specs from djdevNNN.zip, and we needed a way to have
__DJGPP__ and __DJGPP_MINOR__ be still in synch with the library being
used (without telling users to edit their specs files).
> This "feature" thus contradicts the info-pages for -MM, -MMD, -MG
> switches:
>
> `-MM'
> Like `-M' but the output mentions only the user header files
> included with `#include "FILE"'. System header files included
> with `#include <FILE>' are omitted.
I don't know if this is a bug or not. It seems like GCC is treating
-imacros as user header files. Which is probably reasonable in some
situations, but not in this context.
If you can suggest a better way of solving this problem, please do.
At the time, this was discussed on the developers' list, but all other
solutions were met with opposition.
- Raw text -