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

[Erik Schnetter]

On Thursday 16 June 2005 07:59, Tom Goodale wrote:
> On Thu, 16 Jun 2005, Erik Schnetter wrote:
> >> 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.
> >
> > We want to use this information in thorn Formaline and put it e.g.
> > into the output directory.  Comments are not good for this.  Make
> > variables would be better, because these can be accessed by a
> > thorn.
>
> In which case the actual version of the compiler used, and not the
> one found at configure time, would probably be much more useful and
> much less deceptive.

There is no "the actual version", because different parts of the source 
may have been compiled by different compiler versions.  Since we also 
want to store how the configure stage came to its conclusions, and 
since this information is already available (in the configure stage) 
and only needs to be communicated, using the compiler version that the 
configure stage found is a good choice.

-erik

-- 
Erik Schnetter <schnetter at aei.mpg.de>   http://www.aei.mpg.de/~eschnett/

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.cactuscode.org/pipermail/developers/attachments/20050616/bbe0d003/attachment-0002.bin