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

[Bela Szilagyi]

Speaking of versions -- would it be desirable to have Cactus do the job of 
reminding the users of the kind of inconsistencies one gets when 
compiling/configuring with different versions of a given compiler?

Say, we store the version at configure time, and then give a prominent warning 
to the user when compiling with compilers of different versions.

Or, am I overcomplicating this issue?

Bela.

On Thursday 16 June 2005 15:15, Erik Schnetter wrote:
> 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

-- 
Bela Szilagyi
----------------------------------------------------
Max-Planck-Institut für Gravitationsphysik
Albert-Einstein-Institut
Tel: +49 331 567 7632
Fax: +49 331 567 7649
----------------------------------------------------