[MITgcm-devel] mpack no longer working

Jean-Michel Campin jmc at ocean.mit.edu
Sat Feb 23 12:59:43 EST 2008


Hi,

I made a big mess in the mpack build yesterday, and it's no
longer building (e.g., testing results from this morning on
several platforms, including faulks, are missing), and it's
annoying. 
I revert the 1rst changes I made, and apart from an additional dir
"cmulocal", the mpack-1.6 is exactly what it was before.
I can remove this "cmulocal" dir but it does not change anything.

The reason for this "fail to build" is that the 
Makefile behave differently because files have a different 
time of last modification (since I checked-in modifications +
checked-in back the original files), and then it start to 
run "automake" (and may be also "autoconf") which does not work
properly. 

The solution would be to modify the "configure" stage
to create a simpler Makefile which never run the automake/autoconf
program. But it does not seem obvious to me, and in the mean time,
I will check-in fake changes in mpack-1.6 to align the time
of last-modif so that the build can go on without running 
automake/autoconf.

If this works, I will ask you not to check-in changes in
tools/mpack-1.6 . Instead, I would like to check-in in the 
contrib area an mpack_src dir where I will put the patch to 
mpack-1.6-4 ; this will allow to test separately the mpack built 
without messing up all our daily test results.
And any-one will be welcome to check-in fixes there.

Cheers,
Jean-Michel




More information about the MITgcm-devel mailing list