On Fri, Apr 26, 2013, Eugene Yedvabny wrote:
>
> Which brings up a separate issue: THIRDPARTY is called by the serial,
> parallel, and [now] openmp targets regardless of whether the $rism or
> $pbsaflag have been set. But the configure2 script only calls FFTW3's
> configure if we are compiling RISM/PBSA with FFTW. So while there is
> no effective difference (because there are further checks for $rism=no
> within the target), Amber should still only compile FFTW3 if it plans
> on actually using it. The solution would be to remove $(FFTW3) from
> THIRDPARTY and call it conditionally from within the targets.
I'm lost here, probably missing something obvious. If you run configure with
options that skip fftw3 (e.g. with the -nofftw3 flag), the FFTW3 variable in
config.h is blank, so having it in THIRDPARTY doesn't actually lead to
fftw3 being built.
...dac
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Sun Apr 28 2013 - 04:00:02 PDT
