On 2012-03-17, at 12:26 AM, Ross Walker wrote:
> Hi Tyler,
>
>> I think we should have a consistent policy as to what happens when some
>> functionality is not available with a particular compiler or whatever.
>> IMO, I think configure should _always_ die with an error message and
>> explicit instructions on how to proceed. My previous error message
>> would return the user's original configure command modified such that
>> RISM would not be built by adding '-norism' and removing any instances
>> of '-rism'. This way they could copy and paste to quickly get to the
>> next step but also knew exactly what functionality was missing.
>
> The problem is that ./configure -norism gnu no longer works. It still tries
> to build rism because of the dependency on rism that has been introduced in
> the building of libsff. So right now it makes no difference if -norism is
> specific or not - the build process still tries to build FFTW3 and that's
> where it crashes.
I've pushed out a working version that still automatically turns on -norism for older compilers.
I apologize for the problems as this my fault. I tried to clean up the build process a bit and did test the -norism flag (it didn't produced any RISM executables) but neglected to test it with GNU 4.1.2.
I will now re-implement the original error message for configure unless there are any objections.
Tyler
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sat Mar 17 2012 - 09:30:03 PDT
