[MITgcm-support] build problem after cvs update (SOLVED)

[m. r. schaferkotter]

the 'problem' was that i was using a SIZE.h file for a serial run  
rather than an mpi run.


On Jun 28, 2010, at 2:12 PM, m. r. schaferkotter wrote:

> greetings;
>
> i just updated MITgcm via cvs and now a previously successful build  
> procedure elicits:
>
> /opt/cray/xt-asyncpe/3.8/bin/ftn: INFO: linux target is being used
> /opt/pgi/10.3.0/linux86-64/10.3/libso/libpgf90.a(initpar.o): In  
> function `__hpf_initarg':
> initpar.c:(.text+0x137): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> initpar.c:(.text+0x162): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> initpar.c:(.text+0x196): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> initpar.c:(.text+0x1a9): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> initpar.c:(.text+0x1c8): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> /opt/pgi/10.3.0/linux86-64/10.3/libso/libpgf90.a(initpar.o): In  
> function `__hpf_getenv':
> initpar.c:(.text+0x1e5): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> /opt/pgi/10.3.0/linux86-64/10.3/libso/libpgf90.a(initpar.o): In  
> function `__hpf_initopt':
> initpar.c:(.text+0x24f): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> initpar.c:(.text+0x262): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> initpar.c:(.text+0x282): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> initpar.c:(.text+0x2e1): relocation truncated to fit: R_X86_64_PC32  
> against `.bss'
> /opt/pgi/10.3.0/linux86-64/10.3/libso/libpgf90.a(initpar.o): In  
> function `__hpf_getopt':
> initpar.c:(.text+0x324): additional relocation overflows omitted  
> from the output
> make: *** [mitgcmuv] Error 2
>
> the domain extents are 477 440 47.
>
> a colleague reports a successful build on a domain of extents 426  
> 304 47. he has not updated via cvs though.
>
> i/m not sure if the problem is caused by the larger array size or  
> the cvs update.
>
> any ideas?
>
> michael
>
>
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support