Re: Question on multiple compiler environment
- From: Janne Blomqvist <foo@xxxxxxxxxxx>
- Date: Wed, 27 Sep 2006 18:07:14 +0300 (EEST)
In article <efddpe$g5$1@xxxxxxxxxxxxxxxxxxxxxxx>, Matthias Möller wrote:
we are developing a finite element package for the simulation of
compressible and incompressible flows. It is mainly written in Fortran
95 but some external libraries are coded in C and/or F77. The aim is to
write a portable code which runs on many different architectures and
compilers.
Right now, the detection of architectures works quite well. In addition,
the user can specify some meta tags, e.g., use native BLAS, etc. Then
our build system "knows" about the right compiler names, options and
paths to the external libraries.
Unfortunately, for each compiler the (performance) switches vary from
one version to another. Do you have some general idea how to determine
the version number of the compiler in a general fashion? That is, I
already know the compiler's name, e.g., g95, ifort, f95 (SUN) but need
to determine its version.
I have used the collection of autoconf macros and misc related stuff
"stubmake" at http://jonas.iki.fi/index.php#Fortran95 , suitably
modified to use automake instead of manually written Makefiles, for
things like compiler and blas/lapack etc. detection. Works quite well,
although getting up to speed with autotools is a handful. As such, the
macros above don't include tests for compiler versions, but with
autoconf it ought to be straightforward to implement such version
tests (well, as straightforward as doing anything with autoconf can
be..).
--
Janne Blomqvist
.
- References:
- Question on multiple compiler environment
- From: Matthias Möller
- Question on multiple compiler environment
- Prev by Date: Re: Strange Porting Problem CVF to IVF, requesting help and ideas.
- Next by Date: Re: loop debugging Compag Visual Fortran Compiler
- Previous by thread: Re: Question on multiple compiler environment
- Next by thread: profile g95
- Index(es):
Relevant Pages
|
