On Mon, Mar 30, 2009 at 1:35 AM, Mark Williamson <mjw.sdsc.edu> wrote:
> So, where am I going with this...? I see these options:
>
> A) Request gcc.org to implement TR-15581 in gfortran 4.1 and release a bug
> fix as gfortran 4.1.3 .
>
> B) Revert my "fix" and modify AMBER's configure script to reject any version
> of gfortran prior to 4.2.0 .
>
> C) Keep the my current "fix" and allow versions of gfortran prior to 4.2.0 .
>
> Option "A" I think is unlikely, plus, not all distributions may pick up this
> fix. Option "C" seems silly since the compiler version is holding back the
> benefits Joe states above and this problem is not seen in ifort.
>
> I think option "B" would perhaps be the best thing to do [...]
Hi,
I just wanted to mention that, perhaps, the 'silly' option ("C") may
actually be the best one, from the point of view of portability. I can
imagine users trying to install Amber in some older systems, and
getting into trouble because they don't have the latest version of
gfortran (For example, RHEL 4 doens't, as you mention yourself).
Unless, of course, we decide to drop support to all legacy systems at
once...
If we go with option "B", may I suggest a similar check on the
configure_at script as well, to decide whether or not to install gleap
if the gcc version is < 3.4? (I still get bitten by it sometimes :-( )
Gustavo.
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Apr 01 2009 - 01:08:29 PDT
