[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #EAZ-791845]: McX2007

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #EAZ-791845]: McX2007
  • Date: Mon, 02 Jun 2008 17:06:17 -0600
Hi HP,
re: Searching there for "X11" list a number of modules of installed

> Yes, I discovered that as well, gleaning it from my old system. So, this
> is settled and building made some progress until it hit on the g77
> command. This is not found (see attached makelog). This time I am really
> at a loss. I find modules gcc-fortran 4.2 & 4.2.1 as well as libfortran
> 4.2.1 installed. Yast does not give any modules when searching for g77,
> while on the old system I get installed modules for this search string.

I am guessing that g77 is not supported/available under openSUSE 10.3.  No
worries, however, you can use gfortran instead.

> What is missing, i.e. what have I to search for?

Here is what you need to do:

1) make sure that gcc-gfortran is installed (use Yast)

2) verify that your 'mcidas' user's login session can find gfortran:

   <as 'mcidas'>
   which gfortran
   which gcc       <- just for good luck ;-)

3) edit the shell-specific definition file (i.e., .cshrc for C-shell; .profile 
for Bourne
   or Korn shell; .bash_profile for BASH) for 'mcidas' and:

C-shell syntax:

replace:

setenv VENDOR -g77
-- OR --
setenv VENDOR -vendor

with:

setenv VENDOR -gfortran

Bourne/Korn/BASH syntax:

replace:

VENDOR=-g77
export McINST_ROOT VENDOR
-- OR --
VENDOR=-vendor
export McINST_ROOT VENDOR

with:

VENDOR=-gfortran
export McINST_ROOT VENDOR

After making the editing change, log off as 'mcidas' and then log back on
(or 'source .cshrc' for C-shell or . .bash_profile for BASH, etc.).

Once the changes have been made to the environment, then I recommend starting
the build from scratch:

<still as 'mcidas'>
cd ~/mcidas2007/src
make clobber
make

> Sorry to be such a pest, HP

Really, your questions are no problem.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: EAZ-791845
Department: Support McIDAS
Priority: Normal
Status: Closed