Hi,
On Wed, Mar 19, 2014 at 5:27 PM, Timothy J Giese <timothyjgiese.gmail.com>wrote:
> If the user is compiling with the gcc toolchain, netcdf's configure may
> properly determine the use of gcc, but if the name of compiler is funny
> e.g., gfortran44,
> (or maybe because the compiler is REALLY old - I'm not sure of the
> exact reason for the problems I was seeing), problems can occur.
>
Out of curiosity, do you know exactly which compiler and version that you
had problems with?
We could add defines to the netcdf fortran configure line based on
specified compilers, but I hesitate to do that (right before release)
because then we're *always* overriding the netcdf configure script's logic.
I think if we do decide to go this route it needs thorough testing for gnu,
intel, and pgi compilers across multiple platforms. I can start doing some
of these tests tomorrow.
We could maybe instead make it an option to configure named
'-setnetcdfdefine' or something, so if users have problems with the
'normal' configure they can try the option which will explicitly set the
define based on the specified compiler...
-Dan
--
-------------------------
Daniel R. Roe, PhD
Department of Medicinal Chemistry
University of Utah
30 South 2000 East, Room 201
Salt Lake City, UT 84112-5820
http://home.chpc.utah.edu/~cheatham/
(801) 587-9652
(801) 585-6208 (Fax)
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Mar 19 2014 - 17:30:03 PDT
