Re: [AMBER-Developers] lib and lib64

From: Jason Swails <jason.swails.gmail.com>
Date: Thu, 9 Feb 2012 10:32:32 -0500

This doesnt happen for me on any of my systems, so I think it's something common to your particular setup.

We don't actually strictly control the fftw build-- we just call its configure and makefiles. I'm guessing something about your setup is triggering fftw to pit some stuff in lib64, but I dont know what is doing that.

What is your version of autotools and gmake or automake or whatever is being used?

It sounds like what we need to do is copy everything from lib64 if it exists into lib. We may have to do the same for lib32 if that situation exists too.

All the best,
Jason

--
Jason M. Swails
Quantum Theory Project,
University of Florida
Ph.D. Candidate
352-392-4032
On Feb 9, 2012, at 9:59 AM, Andreas Goetz <agoetz.sdsc.edu> wrote:
> Dear all,
> 
> On my openSuSE 12.1 box, two directories are created for libraries,
> $AMBERHOME/lib
> $AMBERHOME/lib64
> 
> In config.h the variable LIBDIR points to $AMBERHOME/lib
> 
> As a consequence the AmberTools and AMBER build fails. Any idea what has been changed in the configure script or Makefiles? This was all working a couple of weeks ago.
> 
> All the best,
> Andy
> 
> --
> Dr. Andreas W. Goetz
> San Diego Supercomputer Center
> Tel  : +1-858-822-4771
> Email: agoetz.sdsc.edu
> Web  : www.awgoetz.de
> 
> 
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers

Received on Thu Feb 09 2012 - 08:00:02 PST