[Developers] Patch: store the version of C/C++/Fortran compilers

[Tom Goodale]

On Thu, 16 Jun 2005, Thomas Radke wrote:

> Tom Goodale wrote:
>>> If you want to trace how configure made its decisions, then you need the
>>> versions as seen by configure.
>> 
>> 
>> If that's the reason for storing the enfo, then fair enough, in which case 
>> it needs to go in a log file, or a comment, but not in a make variable, and 
>> be clearly marked as 'These settings are based upon detecting compiler x, 
>> version y at configuration time.'
>
> I just thought storing the compiler version close to the compiler flags would 
> be most convenient.

True, so how about putting it in as a set of comments above the 
appropriate compiler flags in the make.code.defn, in a format like above. 
This would provide the information with no ambiguity as to what it means.

> Even though the version information might not be needed 
> as makefile variables - but then we already have OS, CPU, and VENDOR in 
> make.config.defn.

These are far less likely to change than compiler version, and are 
potentially used for conditional compilation in thorns' makefiles. 
Although I guess in principle we should also detect these at compile time 
too, and have the configuration-time ones put in comments, however this 
late in the beta cycle I'm not going to change that.

Tom