Hi David,
Okay, thanks. Problem solved by work-around. I am using a rather old but
stable release of ifort (version 8.1, build 20050309Z, l_fc_pc_8.1.025) on a
32 bit xeon. This compiler apparently has a language parsing error and gets
confused by a line continuation construct of the general form:
.....( .......'(' ........ ')' .... &
........)
(ie., it gets lost when it hits the quoted parens instead of the final
parens on the continued line - I have really not broken it down exactly, but
if you merge the line, it parses correctly).
I attached the original and modified code I compiled; I would probably just
use the modified code myself rather than requiring the fixed compiler, but
it is my general philosophy to demand less rather than more of the
compilers - you end up causing yourself less grief in the long run (though
this one is sort of silly...).
It actually looks like there may be some other errors of this sort later on,
so we may be forced to upgrade (I'll see how widespread the problem is
before I ditch the compiler - it would be nice to not have to force people
to ditch this compiler, as it was really pretty good overall).
Regards - Bob
----- Original Message -----
From: "David A. Case" <case.scripps.edu>
To: <amber-developers.scripps.edu>
Sent: Monday, March 24, 2008 7:28 PM
Subject: Re: amber-developers: Build broke?
> On Mon, Mar 24, 2008, Robert Duke wrote:
>
>> Does anyone know what's going on with the current sander tree? I synced
>> up
>> this morning and am dying attempting to compile ncsu-value.f. Is
>> somebody
>> going to check in a fix real soon now, or is there a tarball somewhere I
>> can revert to as a stable copy? (silly me, I did not save the last state
>> I
>> had of the amber 10 tree).
>
> Works for me with several versions of ifort, plus g95. Can you give
> details
> of the error message, compiler version, etc.? As the CVS logs indicate,
> this
> routine has not changed since last December, and people have been building
> sander for months based on it.
>
> Not to say you are wrong, but we (or bugzilla) need details. You can add
> -DDISABLE_NCSU to your AMBERBUILDFLAGS, but I think this just bypasses the
> code execution...it still has to be compiled.
>
> ...dac
>
Received on Fri Apr 18 2008 - 21:13:49 PDT
