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

[McIDAS #MVO-904497]: Build works, but how do you enter McIDAS-X Text commands?



Hi Samuel,

Evidently, you were able to work past the -lX11 link error you reported
previously.  Can you let us know what you did so the information/procedure
will be recorded in our inquiry tracking system?  Thanks in advance...

re:
> I don't see a way to execute these commands to test the build.
> 
> When I hit the "Start McIDAS" button from the mcidasx window, I get the
> following:
> 
> Error in startup script: invalid command name "fileToList"
> while executing "fileToList $mcrcfile"
> (procedure "readMcidasrc" line 139) invoked from within
> "readMcidasrc "$home/.mcidasrc""
> 
> (file "/home/mcidas/mcidas2007/src/mcidas" line 667)

If this is a first time installation of McIDAS, you should go ahead and install
the newly built code before attempting to run the tests.  This is what I meant
in:

Building and Installing McIDAS-X 2007
http://www.unidata.ucar.edu/software/mcidas/current/users_guide/BuildingandInstallingMcIDAS-X.html

  Testing the Build

  The user mcidas can now test the Unidata McIDAS-X 2007 before installing it.

  NOTEs:

    * Testing is recommended if one is upgrading from a previous McIDAS 
installation.

    * If this is a new McIDAS installation, please complete the instructions in 
Installing
      the Distribution now.

      After installing the new build, you can check the functionality of the 
build by executing
      the actions listed in steps 5. through 8. below (i.e., skip steps 1. 
through 4. and 9.). 

In a brand new installation, the Tcl/Tk scripts needed by the MCGUI graphical 
interface
will not be found, and one will run into the problems you report.

So, based on my assumption that this is a brand new McIDAS installation, my
recommendations are:

- go ahead and install the newly built code:

<as 'mcidas'>
cd mcidas2007/src
make install
-- OR -- 
make install.all          <- if you build using 'make all'

- make sure that you have modified the shell-specific definition file as per 
directions
  in:

Preparing the mcidas account
http://www.unidata.ucar.edu/software/mcidas/current/users_guide/PreparingthemcidasAccount.html

- log off and then log back on to make sure that the changes in your 
shell-specific
  definition file are active

- finally run the tests indicated in steps 5-8 outlined in the test 
instructions listed
  in the URL above.

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: MVO-904497
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.