Dear Dr. Case,
Yesterday I added pbsa's libinstall to nab's install rule, so it definitely
can be triggered by Makefile_at. I apologize for the inconveniences.
Best,
--
Mengjuei Hsieh, Molecular Biology & Biochem, Univ. of California Irvine.
> From: case <case.biomaps.rutgers.edu>
> Reply-To: AMBER Developers Mailing List <amber-developers.ambermd.org>
> Date: Tue, 9 Feb 2010 16:06:57 -0500
> To: AMBER Developers Mailing List <amber-developers.ambermd.org>
> Subject: Re: [AMBER-Developers] simplepbsa build errors with commercial
> compilers
>
> On Tue, Feb 09, 2010, Jason Swails wrote:
>>
>> The Makefile has lines
>>
>> simplepbsa$(SFX): simplepbsa.o gopt.o libpbsa.a sfflib syslib netlib
>> c9x-complex
>> $(FC) -nofor_main -o simplepbsa$(SFX) simplepbsa.o gopt.o libpbsa.a \
>> $(LIBDIR)/libsff.a ../lib/nxtsec.o $(FLIBSF) $(LDFLAGS)
>>
>> which are invoked by the top-level Makefile_at.
>
> I guess this is all moot, since MengJeui has been updating things, but I still
> don't see how the top-level Makefile_at (which just does a "make install"
> in the pbsa directory) would trigger anything related to simplepbsa. It
> doesn't for me, on either Linux or Mac, and the compiler seems irrelevant.
>
> Can you see what is going on? I.e. something that is requiring either
> the "libinstall" rule or the "simplepbsa" rule?
>
> ....dac
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Tue Feb 09 2010 - 13:30:04 PST