- To: gembud@xxxxxxxxxxxxxxxx
- Subject: Re: [gembud] [Gempak] GEMPAK installation woes
- From: Austin Cross <austin@xxxxxxxxxxxx>
- Date: Mon, 28 Jan 2008 13:58:49 -0900
That was indeed a problem. Starting fresh, setting up Gemenviron again,
and forcing GEM_COMPTYPE to g77 did the trick. MCHPRM.PRM was pointing
to the correct file. Then it was just a matter of satisfying a couple
more dependencies and it finally compiled successfully.
Thanks for all the help guys, Austin Arthur A. Person wrote:
Austin,I found in the 5.10.3 build that if you built with GFORTRAN (which didn't work for me) and then tried to switch to G77 that the build got confused unless you started from scratch again (i.e. untar the distribution again, set up all your Gemenviron settings as you want them including USE_G77=1 and then rebuild). There's apparently a bug in the cleanup Makefile in this instance. You might give this a try and see if it works.Art On Thu, 24 Jan 2008, Austin Cross wrote:Thanks for the response. It's Debian etch amd64. The output from printenv is at: http://people.iarc.uaf.edu/~austin/printenv.out I notice the GEM_COMPTYPE is wrong. If I use setenv to change that, it seems to find g77 alright. However, there a number of new errors mostly from Fortran parameter statements: http://people.iarc.uaf.edu/~austin/make2.out Austin
-- Austin Cross Graduate Student / Research Assistant International Arctic Research Center University of Alaska Fairbanks
- References:
- [gembud] GEMPAK installation woes
- From: Austin Cross
- Re: [gembud] [Gempak] GEMPAK installation woes
- From: Austin Cross
- Re: [gembud] [Gempak] GEMPAK installation woes
- From: Arthur A. Person
- [gembud] GEMPAK installation woes