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

[Erik Schnetter]

On Thursday 16 June 2005 04:24, Tom Goodale wrote:
> 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.

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.

-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/a43bcddb/attachment-0002.bin