[CP2K:3546] Re: Installing problem with tamc_run.o
Alin Marin Elena
alinm... at gmail.com
Sat Oct 22 11:34:31 UTC 2011
On Saturday 22 October 2011 12:55:35 Teodoro Laino wrote:
> OK- can you try again?
> I've totally cleaned-up the INTENT with POINTER - no idea why there were
> there... Teo
Hi Teo,
I am little bit puzzled... by the error... pointer arguments can have intents
as of fortran2003 standard... I do not doubt that I may have been sloppy with
using them but I am still surprised that ifort 12 and both gfortran 4.5 and
4.6, passed the code as valid...
I will check my code and send you a patched version with intents removed for
pointers.
Alin
>
> On Oct 22, 2011, at 12:03 PM, joanyi Chen wrote:
> > Hi Teo,
> >
> > Thank you!
> >
> > The error is getting smaller!
> >
> > Here's the error after using the new code.
> >
> > fortcom: Error: /home/jnch/cp2k/makefiles/../src/tamc_run.F, line
> > 1035: A pointer dummy argument with the INTENT(IN) attribute shall not
> > appear as an actual argument if the associated dummy argument has the
> > INTENT(OUT) or INTENT(INOUT) attribute. [AVERAGES]
> >
> > CALL
> >
> > HMCsampler(globenv,force_env,averages,r,mc_par,simpar,moves,gmoves,rng_str
> > eam_mc,output_unit,fz,zbuff,error=error)
> > ----------------------------------------^
> > compilation aborted for /home/jnch/cp2k/makefiles/../src/tamc_run.F
> > (code 1)
> > make[1]: *** [tamc_run.o] Error 1
> >
> > Thanks for your reply!
> >
> > Joan
> >
> > On 10月22日, 下午4時23分, Teodoro Laino <teodor... at gmail.com> wrote:
> >> Hi Joan and Alin,
> >>
> >> I guess there was a wild usage of INTENTs in the original source code.
> >> I've just fixed that. Can you please check if its compiling properly now?
> >>
> >> Thanks
> >> Teo
> >>
> >> On Oct 21, 2011, at 6:27 PM, joanyi Chen wrote:
> >>> Dear all,
> >>>
> >>> I try to install cp2k on Linux-SUSE and encoutered some problems.
> >>>
> >>> Here is the error during compiling.
> >>>
> >>> fortcom: Error: /home/jnch/cp2k/makefiles/../src/tamc_run.F, line
> >>> 1036: A pointer dummy argument with the INTENT(IN) attribute shall not
> >>> appear as an actual argument if the associated dummy argument has the
> >>> INTENT(OUT) or INTENT(INOUT) attribute. [AVERAGES]
> >>>
> >>> CALL HMCsampler
> >>>
> >>> (globenv,force_env,averages,r,mc_par,simpar,move,gmoves,rng_stream_mc,ou
> >>> tpu-t_unit,fz,zbuff,error=error)
> >>> -----------------------------------------^
> >>> fortcom: Error: /home/jnch/cp2k/makefiles/../src/tamc_run.F, line
> >>> 1036: This name does not have a type, and must have an explicit
> >>> type. [MOVE]
> >>>
> >>> CALL HMCsampler
> >>>
> >>> (globenv,force_env,averages,r,mc_par,simpar,move,gmoves,rng_stream_mc,ou
> >>> tpu-t_unit,fz,zbuff,error=error)
> >>> ------------------------------------------------------------------^
> >>> fortcom: Error: /home/jnch/cp2k/makefiles/../src/tamc_run.F, line
> >>> 1036: A pointer dummy argument with the INTENT(IN) attribute shall not
> >>> appear as an actual argument if the associated dummy argument has the
> >>> INTENT(OUT) or INTENT(INOUT) attribute. [GMOVES]
> >>>
> >>> CALL HMCsampler
> >>>
> >>> (globenv,force_env,averages,r,mc_par,simpar,move,gmoves,rng_stream_mc,ou
> >>> tpu-t_unit,fz,zbuff,error=error)
> >>> -----------------------------------------------------------------------
> >>> ^
> >>> fortcom: Error: /home/jnch/cp2k/makefiles/../src/tamc_run.F, line
> >>> 1036: A pointer dummy argument may only be argument associated with a
> >>> pointer. [MOVE]
> >>>
> >>> CALL HMCsampler
> >>>
> >>> (globenv,force_env,averages,r,mc_par,simpar,move,gmoves,rng_stream_mc,ou
> >>> tpu-t_unit,fz,zbuff,error=error)
> >>> ------------------------------------------------------------------^
> >>> compilation aborted for /home/jnch/cp2k/makefiles/../src/tamc_run.F
> >>> (code 1)
> >>> make[1]: *** [tamc_run.o] Error 1
> >>>
> >>> I tried some ways to modify the tamc_run.F file, by erasing
> >>> "averages","gmoves" and "move" in the file. Obviously, I'm too naive :
> >>> -)
> >>> I also tried to edit the arch file by adding
> >>> tamc_run.o: tamc_run.F
> >>>
> >>> $(FC) -c $(FCFLAGS2) $<
> >>>
> >>> from the information provided by intel
> >>> http://software.intel.com/en-us/articles/build-cp2k-using-intel-fortr...
> >>> (I read the part of "Known Issues or Limitations", and assumed this
> >>> command would pass the tamc_run.F )
> >>> Still, in vain. What else can I deal with it?
> >>>
> >>> Thank you very much!
> >>>
> >>> Joan
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> >>> Groups "cp2k" group. To post to this group, send email to
> >>> cp... at googlegroups.com.
> >>> To unsubscribe from this group, send email to
> >>> cp2k+uns... at googlegroups.com. For more options, visit this group
> >>> athttp://groups.google.com/group/cp2k?hl=en.- 隱藏被引用文字 ->>
> >> - 顯示被引用文字 -
--
Without Questions there are no Answers!
______________________________________________________________________
Alin Marin ELENA
Advanced Molecular Simulation Research Laboratory
School of Physics, University College Dublin
----
Ardionsamblú Móilíneach Saotharlann Taighde
Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath
-----------------------------------------------------------------------------------
http://alin.elenaworld.net
______________________________________________________________________
More information about the CP2K-user
mailing list