From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: make depend Date: 18 Jan 2000 13:36:41 GMT Organization: Aachen University of Technology (RWTH) Lines: 26 Message-ID: <861q99$kdr$1@nets3.rz.RWTH-Aachen.DE> References: NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 948202601 20923 137.226.32.75 (18 Jan 2000 13:36:41 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 18 Jan 2000 13:36:41 GMT User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586)) Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Gisle Vanem wrote: > Andris Pavenis >> 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.