Mail Archives: djgpp/2000/01/18/18:58:26
Gisle Vanem <giva AT bryggen DOT bgnett DOT no> wrote:
> Andris Pavenis <pavenis AT lanet DOT lv>
>> 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).
Because 'specs' *cannot* be updated for a new version of DJGPP. It
would require manual editing by the person installing DJGPP, and lead
to a whole host of new way people would find to break their DJGPP
installations in unforeseen ways.
'specs' is part of the gcc packages, which is meant to be
independently exchangeable. I.e. it cannot be nailed to one specific
version of DJGPP. You're supposed to be able to switch either your
DJGPP version (djdev*.zip, that is) or your gcc, without having to
fiddle with the files of the other one. For quite some time, we
managed to get along by having 'specs' be part of the DJGPP, not the
gcc package, but given the changes to 'specs' introduced by newer
gcc's, that became a non-option.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -