[MITgcm-support] problem running on OS X

samar khatiwala spk at ldeo.columbia.edu
Wed Aug 4 11:08:09 EDT 2004


Chris, thanks! That was indeed the problem. But it took me 3 cvs co
attempts to get a fully functional installation.

This appears not to be a problem with cvs on my Mac since I get similar
behavior on a Linux box. For instance 'checkpoint53' would not appear at
the beginning of the output. Even worse, the first time I checked out
c53 (last week) on the Linux machine it would not even compile because the
monitor pkg had not been checked out! Anyway, after several attempts I now
seem to have a full installation on the Linux box too. Never had
such problems before.

I don't really know how cvs works to tell if this is a problem with my
clients or your server. (Would be funny though to get the same problem
on two different platforms.) For instance, when does cvs replace $ tags?
Is it done by the server or the clients? For some reason $Name is not
being correctly replaced in eeintro_msg.F.

Samar

On Mon, 2 Aug 2004, Chris Hill wrote:

> Samar,
>
>  I just noticed one other thing in your output. At the top there is a line
>
> PID.TID 0000.0001) // MITgcm UV Release: $Name:  $
>
>  for a clean checkout of checkpoint53 this is supposed to read
>
> PID.TID 0000.0001) // MITgcm UV Release: $Name: checkpoint53 $
>
>  Its not clear that this has anything to do with your problem, but if you
> have a moment could you do an exp0 run in
>  a clean directory
>  e.g
>
>  cvs co -d c53 -r checkpoint53 MITgcm/
>  etc....
>
>  That might give another clue.
>
> Thanks,
>
> Chris
> > -----Original Message-----
> > From: mitgcm-support-bounces at mitgcm.org
> > [mailto:mitgcm-support-bounces at mitgcm.org] On Behalf Of Chris Hill
> > Sent: Monday, August 02, 2004 8:26 PM
> > To: mitgcm-support at mitgcm.org
> > Subject: RE: [MITgcm-support] problem running on OS X
> >
> > Hi Samar,
> >
> >  I looked at your output file. There are some things that
> > look really weird early on - like the maximum Y coord for a
> > cell center is printed to be 10^63 and fCori reaches 10^52
> > (which is roughly beta*10^63). Funnily the x coordinates look
> > fine. The good news is that setting YC only involves the
> > initialization name lists, the bad news is that, at the
> > moment, I'm not sure how the YC numbers are getting so crazy.
> >
> > Chris
> >
> > > -----Original Message-----
> > > From: mitgcm-support-bounces at mitgcm.org
> > > [mailto:mitgcm-support-bounces at mitgcm.org] On Behalf Of samar
> > > khatiwala
> > > Sent: Sunday, August 01, 2004 12:10 AM
> > > To: mitgcm-support at mitgcm.org
> > > Subject: RE: [MITgcm-support] problem running on OS X
> > >
> > > Hi Chris
> > >
> > > I tried the -xassembler option (and also NML_TERMINATOR).
> > It did not
> > > fix the problem. As you said, it was a long shot. cpp without it
> > > hasn't given problems on other code.
> > > FYI: previous versions - I have been working with c51h_pre
> > and c52 -
> > > work fine with absoft on OS 10.3.x.
> > >
> > > Thanks, Samar
> > >
> > > On Sat, 31 Jul 2004, Chris Hill wrote:
> > >
> > > > Hi Samar,
> > > >
> > > >  not sure if this helps but I did do some runs recently on
> > > a mac with xlf.
> > > >
> > > >  One problem was with cpp in panther which may also affect
> > > absoft also
> > > > see CPP line -xassembler option below. The other options
> > > are probably
> > > > xlf specific.
> > > >
> > > >  I will see if I can find an absoft machine.
> > > >
> > > > Chris
> > > >
> > > > Darwin_ppc_xlf_panther
> > > > #!/bin/bash
> > > >
> > > > # $Header:
> > > > /u/gcmpack/MITgcm/tools/build_options/darwin_ppc_xlf_panther,v
> > > > 1.1 2004/06/30 01:00:37 cnh Exp $
> > > > #
> > > > # Build options for Darwin on G5 Mac with IBM XL Fortran
> > > compilers #
> > > > tested on G5 dual, 2GHz # ( Darwin
> > eaps-dhcp-162.lcs.mit.edu 6.7.5
> > > > Darwin Kernel Version 6.7.5: Mon Aug 11 19:28:40 PDT 2003;
> > > > root:xnu/xnu-344.21.73.obj~1/RELEASE_PPC  Power Macintosh
> > > powerpc ) #
> > > > cc-compiler is available only with the Apple Developer
> > Tools, # so
> > > > make sure that those are installed # # **NOTES**
> > > > #   o with Darwin you must remember to build on a ufs file
> > > system. The
> > > > default Darwin file system (hfs) treats
> > > > #     upper case and lower case file names as the same
> > > file. This breaks the
> > > > current MITgcm build procedure.
> > > > #   o tim.c should use uembellished cloc() are the
> > > procedure name for XLF
> > > > #     ETIME (timers.F) and FDATE (utils.F) are not
> > > available with Darwin+XLF
> > > > so need to be switched out.
> > > > #
> > > >
> > > > CPP='/usr/bin/cpp -traditional -P -xassembler-with-cpp'
> > > > FC=/opt/ibmcmp/xlf/8.1/bin/f77
> > > > LINK=/opt/ibmcmp/xlf/8.1/bin/f77
> > > > FFLAGS='-qfixed=132 -qsuffix=f=for'
> > > > FOPTIM='-O3'
> > > > NOOPTFLAGS='-O0'
> > > >
> > > > S64='$(TOOLSDIR)/set64bitConst.sh'
> > > > MAKEDEPEND='${TOOLSDIR}/xmakedepend'
> > > > #MAKEDEPEND=makedepend
> > > > DEFINES='-DWORDLENGTH=4 -DNML_TERMINATOR=" /"'
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: mitgcm-support-bounces at mitgcm.org
> > > > > [mailto:mitgcm-support-bounces at mitgcm.org] On Behalf Of samar
> > > > > khatiwala
> > > > > Sent: Tuesday, July 27, 2004 4:55 PM
> > > > > To: MITgcm-support
> > > > > Subject: Re: [MITgcm-support] problem running on OS X
> > > > >
> > > > > On Tue, 27 Jul 2004, Ed Hill wrote:
> > > > >
> > > > > > We're currently Mac-less but hope to get one for testing
> > > > > purposes.  If
> > > > > > you had one that we could SSH into, that would be *very*
> > > > > helpful.  It
> > > > > > would make it a lot easier to keep our Mac build up-to-date!
> > > > >
> > > > > Hi Ed
> > > > >
> > > > > I'm running the model on my powerbook so this may be hard to
> > > > > arrange. However, I have an older desktop G4 I can give
> > > you access
> > > > > to. I'll set up an account for you.
> > > > >
> > > > > Samar
> > > > >
> > > > > _______________________________________________
> > > > > MITgcm-support mailing list
> > > > > MITgcm-support at mitgcm.org
> > > > > http://dev.mitgcm.org/mailman/listinfo/mitgcm-support
> > > > >
> > > >
> > > > _______________________________________________
> > > > MITgcm-support mailing list
> > > > MITgcm-support at mitgcm.org
> > > > http://dev.mitgcm.org/mailman/listinfo/mitgcm-support
> > > >
> > > _______________________________________________
> > > MITgcm-support mailing list
> > > MITgcm-support at mitgcm.org
> > > http://dev.mitgcm.org/mailman/listinfo/mitgcm-support
> > >
> >
> > _______________________________________________
> > MITgcm-support mailing list
> > MITgcm-support at mitgcm.org
> > http://dev.mitgcm.org/mailman/listinfo/mitgcm-support
> >
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-support
>



More information about the MITgcm-support mailing list