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

[McIDAS #MET-935016]: McIDAS - Cannot get mcunpack to execute -- keep getting message to define McINST_ROOT



Hi Alan,

re:
> Thank you for your help previously.  I had to delay the McIDAS
> installation for just a bit, but now am attempting it again.
> In the meantime I learned a bit more about Fedora and file
> structures, modification of the .bashrc file, etc.


No worries.

> I still am having problems getting the mcunpack program to
> execute.
> 
> I modified the .bashrc filr in the /home/mcidas account to read:
> 
> # .bashrc
> 
> # User specific aliases and functions
> 
> # McINST_ROOT and VENDOR non-conforming shell definitions
> McINST_ROOT=/home/mcidas
> VENDOR=-g77
> if [ -d $HOME/admin/mcidas_env.csh ]; then
> source $HOME/admin/mcidas_env.csh
> fi
> 
> # Source global definitions
> if [ -f /etc/bashrc ]; then
> . /etc/bashrc
> fi

The piece that might be missing is exporting your environment variable
definitions.  Here is the example from the McIDAS installation pages
from our website:

http://www.unidata.ucar.edu/software/mcidas/2005/users_guide/PreparingthemcidasAccount.html#22841

# McINST_ROOT and VENDOR conforming shell defines needed to bulid McIDAS
McINST_ROOT=$HOME
VENDOR=-g77
export McINST_ROOT VENDOR
if [ -e $HOME/admin/mcidas_env.sh ]; then
  . $HOME/admin/mcidas_env.sh
fi

Without the 'export McINST_ROOT VENDOR' line, these environment variables
will not be picked up by shell scripts (like mcunpack) run from the command
line.

> I had to change the conditional statement to be of similar
> syntax--otherwise I would obtain an error.  This .bashrc did
> work to the the environment variables that were required.
> 
> Below, I copy in what I obtained from the terminal window:
> 
> address@hidden ~]$ pwd
> /home/mcidas
> address@hidden ~]$ echo $McINST_ROOT
> /home/mcidas
> address@hidden ~]$ echo $VENDOR
> -g77
> address@hidden ~]$ ./mcunpack
> You must define McINST_ROOT as the full pathname of an
> existing directory where you intend to install Unidata
> McIDAS-X Version v2005 first. The standard location is
> /home/mcidas.
> 
> Please define McINST_ROOT and try again...
> address@hidden ~]$
> address@hidden ~]$


I believe that this is most likely caused by the lack of the 'export'
line in your .bashrc file.

> So, I do have the directory set up correctly (i. e., I am
> working in the /home/mcidas directory).  the names for
> McINST_ROOT and VENDOR have been set for the mcunpack program
> to use.   Also, mcunpack permissions have been set for it to
> execute.  Still, though, no cigar.  Any ideas?
> 
> Many thanks,...Alan
> --------------------------------------------------------------------------------
> 
> Alan E. Stewart, Ph. D.
> Associate Professor
> The University of Georgia
> Department of Counseling & Human Development
> 402 Aderhold Hall
> Athens, Georgia 30602-7142
> 
> Vox: 706.542.1263
> Fax: 706.542.4130
> 
> Note New Email Address: address@hidden

Thanks for the updated email address.

Please let me know if adding the 'export' line to your .bashrc
file and then doing an '. .bashrc' doesn't get you past the problem
of executing 'mcunpack'.


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: MET-935016
Department: Support McIDAS
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.