It worth bugfix probably. I have got the same error.
Best regards,
Andrew
14.10.2011, 07:34, "Josmar R. da Rocha" <bije_br.yahoo.com.br>:
> 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
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Thu Nov 03 2011 - 03:00:02 PDT
