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.
All the best
Ross
/\
\/
|\oss Walker
---------------------------------------------------------
| Assistant Research Professor |
| San Diego Supercomputer Center |
| Adjunct Assistant Professor |
| Dept. of Chemistry and Biochemistry |
| University of California San Diego |
| NVIDIA Fellow |
|
http://www.rosswalker.co.uk |
http://www.wmd-lab.org/ |
| Tel: +1 858 822 0854 | EMail:- ross.rosswalker.co.uk |
---------------------------------------------------------
Note: Electronic Mail is not secure, has no guarantee of delivery, may not
be read every day, and should not be used for urgent or sensitive issues.
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Mar 16 2012 - 21:30:02 PDT
