Hi Tyler,
That solved the problem and I got AT1.5 installed. Thank you very much for your help!
--- Em qui, 13/10/11, Tyler Luchko <tluchko.rci.rutgers.edu> escreveu:
De: Tyler Luchko <tluchko.rci.rutgers.edu>
Assunto: Re: [AMBER] safemem.o error while compiling Ambertools 1.5
Para: "AMBER Mailing List" <amber.ambermd.org>
Data: Quinta-feira, 13 de Outubro de 2011, 21:05
On 10/13/2011 06:35 PM, Josmar R. da Rocha wrote:
> Dear amber users,
> I got an error when I tried to compile the AmberTools 1.5 in a server with 24 GB ECC RAM and two Tesla C2070, after having patched it with the bugfix.all.
>
> make[1]: Entering directory `/usr/local/amber11/AmberTools/src/rism'
> cpp -traditional -P -DBINTRAJ -DRISM -DRISM_CRDINTERP -DRISM_DX
> -DRISM_LINPROJ rism_report_c.f> _rism_report_c.f
> gfortran -c -O3 -mtune=generic -ffree-form -o rism_report_c.o _rism_report_c.f
> cpp -traditional -P -DBINTRAJ -DRISM -DRISM_CRDINTERP -DRISM_DX
> -DRISM_LINPROJ safemem.f> _safemem.f
> gfortran -c -O3 -mtune=generic -ffree-form -o safemem.o _safemem.f
> _safemem.f:105.40:
>
> type(memTracker),private :: totalMem
> 1
> Error: Object 'totalmem' at (1) must have the SAVE attribute for
> default initialization of a component
> make[1]: *** [safemem.o] Error 1
> make[1]: Leaving directory `/usr/local/amber11/AmberTools/src/rism'
> make: *** [serial] Error 2
>
> The gcc version is 4.4.4 20100503 (Red Hat 4.4.4-2) running in Fedora 13 x86_64.
> In the second server, that has 8 GB ECC RAM, the previous version of
> AmberTools (AT-1.4) was installed. I renamed the folder and so tried
> to install the new version and so the same error was appears. I think
> the problem is due to ECC memory, because we have workstations with
> Non-ECC memory and the AmberTools-1.5 + Amber11 were compilled without
> any problem.
> Do you have any guess on how can I solve it?
>
Hi Josmar,
I'm not sure why you are getting a compile error here but as a quick
fix. Try changing the offending line in safemem.f (not _safemem.f) to read
type(memTracker),private,save :: totalMem
Testing this locally, it doesn't change output at all. Worst case
scenario, memory usage reports by RISM will be incorrect.
I will check into the source of this error but I doubt this has anything
to do with hardware.
Hope this helps,
Tyler
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Thu Oct 13 2011 - 21:00:02 PDT
