Dear Dr. Case,
Thank you very much for your kind help. If the errors and warnings
would not effect on correctly running sander etc, then I am now moving
to compile the mpi version.
Thanks again,
Wen
Quoting "David A. Case" <case.biomaps.rutgers.edu>:
> On Mon, Dec 22, 2008, wl2290.columbia.edu wrote:
>>
>> ./configure_amber -static gfortran -> successful
>
> Great...I'm glad things are working. At the worst, it looks like in
> some circumstances you have problems compiling elsize:
>
>> g++ -c -DBINTRAJ -I../netcdf/include -o elsize.o elsize.cc
>> make[1]: Leaving directory `/opt/amber10/src/etc'
>
> Above it looks like it worked. Then in the next attachment:
>
>> ...
>> ...
>
> It's not easy to see what command is being executed for the following
> types of errors.
>
>> /usr/include/c++/4.1.2/bits/ios_base.h: In member function ???void
>> std::ios_base::_Callback_list::_M_add_reference()???:
>> make[1]: *** [elsize.o] Error 1
>
> But, in this run, elsize was not correctly made.
>
> Good news, however: (1) The first time it worked, so use that; (2)
> elsize is very rarely used anyway, so it's likely you will never miss
> it.
>
> For Amber11, we have rewritten elsize as a C program which is a lot more
> portable. [It's not the language per se, but it is true (in my
> experience) that C++ can be abused to give code that is both
> compiler-dependent and which gives compiler errors in other environments
> that are very hard to track down.]
>
> ...dac
> -----------------------------------------------------------------------
> The AMBER Mail Reflector
> To post, send mail to amber.scripps.edu
> To unsubscribe, send "unsubscribe amber" (in the *body* of the email)
> to majordomo.scripps.edu
>
>
-----------------------------------------------------------------------
The AMBER Mail Reflector
To post, send mail to amber.scripps.edu
To unsubscribe, send "unsubscribe amber" (in the *body* of the email)
to majordomo.scripps.edu
Received on Wed Dec 24 2008 - 01:19:47 PST
