[MITgcm-support] [EXTERNAL] Re: Compiling Problems

Madeleine Youngs myoungs at umd.edu
Tue Aug 20 18:44:12 EDT 2024


Hi Ou, All,

This solved the compilation issues! The old header file was floating around causing issues.   Thank you for your help!

Madeleine

> On Aug 20, 2024, at 3:01 PM, Wang, Ou (US 329B) <ou.wang at jpl.nasa.gov> wrote:
> 
> Hi Madeleine, 
>  
> Thanks for posting the two files that are related to your original posting regarding missing variables, such as diagMdsDir. Based on diagnostics_ini_io.f, which includes the header file DIAGNOSTICS.h, it appears that you are using an old version of DIAGNOSTICS.h that is not consistent with diagnostics_ini_io.F. In particular, I believe the version of DIAGNOSTICS.h you’re using is from https://github.com/MITgcm/MITgcm/commit/8a1f6fb317a4e4d7541359ca41ed638a2ea88ce5, as the diagnostics_ini_io.f file has the following line:
> C $Header: /u/gcmpack/MITgcm/pkg/diagnostics/DIAGNOSTICS.h,v 1.20 2013/08/14 00:54:05 jmc Exp $
> This version of DIAGNOSTICS.h does not declare the missing variables, e.g., diagMdsDir, and therefore the compilation will fail. Please use an up-to-date version of DIAGNOSTICS.h that is consistent with your diagnostics_ini_io.F.
>  
> Best,
> Ou Wang
>  
> From: MITgcm-support <mitgcm-support-bounces at mitgcm.org <mailto:mitgcm-support-bounces at mitgcm.org>> on behalf of Madeleine Youngs <myoungs at umd.edu <mailto:myoungs at umd.edu>>
> Date: Tuesday, August 20, 2024 at 1:59 PM
> To: mitgcm-support at mitgcm.org <mailto:mitgcm-support at mitgcm.org> <mitgcm-support at mitgcm.org <mailto:mitgcm-support at mitgcm.org>>
> Cc: dbonan at caltech.edu <mailto:dbonan at caltech.edu> <dbonan at caltech.edu <mailto:dbonan at caltech.edu>>
> Subject: Re: [MITgcm-support] [EXTERNAL] Re: Compiling Problems
> 
> Here are the files requested. 
>  
>  
> On Aug 13, 2024, at 8:51 PM, Madeleine Youngs <myoungs at umd.edu <mailto:myoungs at umd.edu>> wrote:
>  
> Hi Everyone, 
>  
> I am working on compiling checkpoint68y on Derecho using no opt file (?) and I am getting this error.  Any advice on what the issue is?
>  
>  
> mpif90 -W0 -WB -msse2 -convert big_endian -assume byterecl -O2 -align -lmpich -lnetcdff -lnetcdf  -c diagnostics_fract_fill.f
> cat diagnostics_ini_io.F |  cpp  -traditional -P -DALLOW_USE_MPI -DALWAYS_USE_MPI -DWORDLENGTH=4 -DALLOW_USE_MPI -DHAVE_SYSTEM -DHAVE_FDATE -DHAVE_ETIME_FCT -DHAVE_CLOC -DHAVE_SETRLSTK -DHAVE_SIGREG -DHAVE_STAT -DHAVE_FLUSH  -I.  | ../../../tools/set64bitConst.sh  > diagnostics_ini_io.f
> mpif90 -W0 -WB -msse2 -convert big_endian -assume byterecl -O2 -align -lmpich -lnetcdff -lnetcdf  -c diagnostics_ini_io.f
> Cannot disable Fortran error message 6404
> diagnostics_ini_io.f(2005): error #6404: This name does not have a type, and must have an explicit type.   [DIAGMDSDIR]
>       IF ( diag_mdsio .AND. (diagMdsDir.NE.' ') .AND.
> -----------------------------^
> Cannot disable Fortran error message 6404
> diagnostics_ini_io.f(2006): error #6404: This name does not have a type, and must have an explicit type.   [DIAGMDSDIRCREATE]
>      &     diagMdsDirCreate .AND. (mdsioLocalDir.EQ.' ') ) THEN
> -----------^
> Cannot disable Fortran error message 6514
> diagnostics_ini_io.f(2009): error #6514: Substring or array slice notation requires CHARACTER type or array.   [DIAGMDSDIR]
>         WRITE(namBuf,'(3A)') ' mkdir -p ', diagMdsDir(1:iL), ' '
> -------------------------------------------^
> compilation aborted for diagnostics_ini_io.f (code 1)
> make[1]: *** [Makefile:1776: diagnostics_ini_io.o] Error 1
> make[1]: Leaving directory '/glade/derecho/scratch/myoungs/MITgcm/MultiWidthExperiments/Present9.20.16/build'
> make: *** [Makefile:1688: fwd_exe_target] Error 2
>  
> 
>  
> 
> Thanks,
> Madeleine
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support <https://urldefense.us/v3/__http:/mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!PvBDto6Hs4WbVuu7!NnRx5vlbDYZWIRraW2gZnWzzXsE782jeSZ_0N-DP52xAVkHbj-uEwC3rZ_U5PHL8Ay0r9294n_QD_GmOPdGy$>
>  
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support <https://urldefense.us/v3/__http:/mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!PvBDto6Hs4WbVuu7!NnRx5vlbDYZWIRraW2gZnWzzXsE782jeSZ_0N-DP52xAVkHbj-uEwC3rZ_U5PHL8Ay0r9294n_QD_GmOPdGy$>
>  
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support <https://urldefense.us/v3/__http:/mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!PvBDto6Hs4WbVuu7!N15SMRSDHusDwG0iUnHuzvgHvGSCoOaUki6NUan4Czv9NRP0rF7OGjELWU6BPLmzi_MP9ryN_bnRWM1PrfC5$>
>  
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support <https://urldefense.us/v3/__http:/mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!PvBDto6Hs4WbVuu7!N15SMRSDHusDwG0iUnHuzvgHvGSCoOaUki6NUan4Czv9NRP0rF7OGjELWU6BPLmzi_MP9ryN_bnRWM1PrfC5$>
>  
>  
>  
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20240820/4ad814e6/attachment-0001.html>


More information about the MITgcm-support mailing list