[MITgcm-support] Make Depend: does not symbolic link the needed files

Dierk Polzin dtpolzin at wisc.edu
Fri Nov 15 13:50:25 EST 2013


I have fixed it... Apparently I was in a directory system that this links did not work.. only these files for some reason... 
When I moved to the original file system it compiled...
Argggh

On Nov 15, 2013, at 2:57 AM, Martin Losch wrote:

> Dierk,
> at what stage (after which make command) does this error occur? 
> 
> can you create properly working symbolic links "by hand" on your system (with ln -s)? It looks to me like a error unrelated to genmake2, but rather to you system.
> 
> Martin
> 
> On Nov 14, 2013, at 5:42 PM, Dierk Polzin <dtpolzin at wisc.edu> wrote:
> 
>> After I run genmake using ifort I have run into a problem that all the files needed to be symbolically linked are broken..
>> 
>> Where do I look in genmake2 to fix this?
>> 
>> ls: cannot read symbolic link o2_surfforcing.F: Protocol error
>> ls: cannot read symbolic link mnc_cw_missingvals.F: Protocol error
>> ls: cannot read symbolic link RECIP_DYF_MACROS.h: Protocol error
>> ls: cannot read symbolic link initialise_varia.F: Protocol error
>> ls: cannot read symbolic link RECIP_DYG_MACROS.h: Protocol error
>> ls: cannot read symbolic link TANPHIATV_MACROS.h: Protocol error
>> ls: cannot read symbolic link MNC_CW_READWRITE_I.F: Protocol error
>> ls: cannot read symbolic link RECIP_DYC_MACROS.h: Protocol error
>> ls: cannot read symbolic link RECIP_DXV_MACROS.h: Protocol error
>> ls: cannot read symbolic link TANPHIATU_MACROS.h: Protocol error
>> ls: cannot read symbolic link mom_hdissip.F: Protocol error
>> ls: cannot read symbolic link external_forcing.F: Protocol error
>> ls: cannot read symbolic link gchem_init_fixed.F: Protocol error
>> ls: cannot read symbolic link gmredi_mnc_init.F: Protocol error
>> ls: cannot read symbolic link mon_set_iounit.F: Protocol error
>> ls: cannot read symbolic link adams_bashforth3.F: Protocol error
>> ls: cannot read symbolic link rbcs_add_tendency.F: Protocol error
>> ls: cannot read symbolic link mdsio_writefield.F: Protocol error
>> ls: cannot read symbolic link initialise_fixed.F: Protocol error
>> ls: cannot read symbolic link RECIP_DYU_MACROS.h: Protocol error
>> ls: cannot read symbolic link adams_bashforth2.F: Protocol error
>> ls: cannot read symbolic link mom_calc_ke.F: Protocol error
>> ls: cannot read symbolic link mdsio_readvector.F: Protocol error
>> ls: cannot read symbolic link prestopres.F: Protocol error
>> ls: cannot read symbolic link exch_uv_r8_cube.F: Protocol error
>> ls: cannot read symbolic link RECIP_DXF_MACROS.h: Protocol error
>> ls: cannot read symbolic link mdsio_writelocal.F: Protocol error
>> ls: cannot read symbolic link RECIP_DXG_MACROS.h: Protocol error
>> ls: cannot read symbolic link exch_uv_r4_cube.F: Protocol error
>> ls: cannot read symbolic link RECIP_DXC_MACROS.h: Protocol error
>> ls: cannot read symbolic link exch_uv_rs_cube.F: Protocol error
>> ls: cannot read symbolic link exch_uv_rl_cube.F: Protocol error
>> ls: cannot read symbolic link calc_diffusivity.F: Protocol error
>> ls: cannot read symbolic link ptracers_init.F: Protocol error
>> ls: cannot read symbolic link pressure_for_eos.F: Protocol error
>> 
>> Thanks Dierk
>> 
>> 
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-support
> 
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support




More information about the MITgcm-support mailing list