Re: [AMBER-Developers] First AmberTools release candidate

From: Ben Roberts <>
Date: Tue, 16 Mar 2010 17:22:08 -0400

I got the following grumble from my system (Intel 11.1.084, Mac OS 10.6.2):

./nab -c
./nab -c
./nab -c
./nab -c
./nab -c
if [ "/Applications/AmberTools/2010-03-16/lib/libfftw2xf_intel.a" = '/Applications/AmberTools/2010-03-16/lib/libfftw2xf_intel.a' ]; then\
                cd /opt/intel/Compiler/11.1/084/Frameworks/mkl/interfaces/fftw2xf && make libi386 \
                compiler=intel PRECISION=MKL_DOUBLE \
                INSTALL_DIR=/Applications/AmberTools/2010-03-16/lib; \
        else \
                cd ../fftw-2.1.5 && make install; \
make[2]: *** No rule to make target `libi386'. Stop.
make[1]: *** [/Applications/AmberTools/2010-03-16/lib/libfftw2xf_intel.a] Error 2
make: *** [serial] Error 2

On inspection, it seems that "make libi386" should in that context be
replaced with "make lib32" or, more likely, "make libem64t".

> 3. The AmberTools.pdf file is up-to-date as of 16 Mar. But it still needs
> lots of work.

What's the best way to edit AmberTools.lyx following proof-reading (about
all I feel I can usefully contribute to it at present)? Is the CVS tree
still open to edits in documentation, or is there some other preferred

AMBER-Developers mailing list
Received on Tue Mar 16 2010 - 14:30:03 PDT
Custom Search