[Wrf-users] Wrf-users Digest, Vol 79, Issue 19

[Thomas Schwitalla]

Dear Maria,

the problems are the "intent(in)" and "intent(out)" statements at line 
2363/2364 of dyn_em/module_initialize_real.F . Try to delete the intent 
statements, it should help for gfortran 4.2.4. The other way would be to 
upgrade to gfortran 4.3.x which can handle these pointer declarations 
without problems.

Best regards,
Thomas

Am 16.03.2011 20:53, schrieb wrf-users-request at ucar.edu:
> Message: 3
> Date: Tue, 15 Mar 2011 14:28:06 -0400
> From: Maria Eugenia<maria.frediani at gmail.com>
> Subject: [Wrf-users] problem installing wrf v3.2.1 with gcc v4.2.4
> To: wrf-users at ucar.edu
> Message-ID:
> 	<AANLkTintxGBWArE5O6AjUs09wa4-jST6sq03LiC-F=AP at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Dear all,
>
> I'm trying to install WRFV3.2.1 (dmpar, without support for grib2 io)
> in a SGI Altix 3700 IA64 Itanium 2.
> I'm using gcc/gfortran v 4.2.4, netcdf v4.1.1, mpich2 v1.3.2 and libpng v1.2.12.
> I have successfully built WRF V3.2, with the above configuration, but
> the newest version does not compile completely.
>
> After compiling for em_real, I only have wrf.exe in the WRFV3/main
> directory, no real.exe nor any of the other executables that should be
> there. I don't understand why wrf.exe compiles and real.exe
> doesn't....
>
> I also tried to compile it serial only, to exclude a possible problem
> with mpich2, but the result is the same.
> Maybe it is relevant to mention that ggc is not the default compiler,
> the default is ifort 9.0. However I have checked the paths and
> installed the required softwares with gcc (netcdf,mpich2,libpng).
> Besides that, when I run ./configure, I only see options to use intel
> compiler:
>     1.  Linux SGI Altix, ifort compiler with icc 9.x,10.x  (serial)
>     2.  Linux SGI Altix, ifort compiler with icc 9.x,10.x  (smpar)
>     3.  Linux SGI Altix, ifort compiler with icc 9.x,10.x  (dmpar)
>     4.  Linux SGI Altix, ifort compiler with icc 9.x,10.x  (dm+sm)
> Therefore I created my configure.wrf file based on gcc. Anyway, I
> don't believe this is the problem given that I successfully built v3.2
> with the same configuration.
>
> The configure.wrf file for the serial and dmpar build are attached as
> well as the compile.log.
> I sincerely appreciate your help.
>
> Maria E. B. Frediani
> -------------------------------------------------------------------------------------
> Visiting Scholar
> University of Connecticut
> School of Engineering
> 261 Glenbrook Rd
> Storrs, CT 06269
> frediani at engr.uconn.edu
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: configure.wrfv3.2.1_x86_64_gfortran_gcc_serial
> Type: application/octet-stream
> Size: 19317 bytes
> Desc: not available
> Url : http://mailman.ucar.edu/pipermail/wrf-users/attachments/20110315/fbbd2fa2/attachment.obj
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: compile.log.wrfv3.2.1.serial
> Type: application/octet-stream
> Size: 492280 bytes
> Desc: not available
> Url : http://mailman.ucar.edu/pipermail/wrf-users/attachments/20110315/fbbd2fa2/attachment-0001.obj
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: configure.wrfv3.2.1_x86_64_gfortran_gcc_dmpar
> Type: application/octet-stream
> Size: 19428 bytes
> Desc: not available
> Url : http://mailman.ucar.edu/pipermail/wrf-users/attachments/20110315/fbbd2fa2/attachment-0002.obj
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: compile.log.wrfv3.2.1.dmpar
> Type: application/octet-stream
> Size: 509771 bytes
> Desc: not available
> Url : http://mailman.ucar.edu/pipermail/wrf-users/attachments/20110315/fbbd2fa2/attachment-0003.obj
>
> ------------------------------
>
> _______________________________________________
> Wrf-users mailing list
> Wrf-users at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/wrf-users
>
>
> End of Wrf-users Digest, Vol 79, Issue 19
> *****************************************