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

20040312: McIDAS problem at UPR (cont.)

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: 20040312: McIDAS problem at UPR (cont.)
  • Date: Fri, 12 Mar 2004 14:12:50 -0700
>From: "Luis A. Lopez" <address@hidden>
>Organization: UPR
>Keywords: 200403112135.i2BLZbrV022391 McIDAS

Hi Luis,

>Thank you for your answer, I'll be working with Mcidas this weekend and
>I'll let you know what happened.

Sounds good.  I read email over the weekend, so please don't hesitate
to send in questions when you run into things.

>I don't remember if I told you, but
>the first problem that I'm getting is that Mcidas can't find 
>'mcinst.tar' or 'mcinst.tar.Z', probably after following your
>instructions it will work fine.  Thanks again for your support.

Yes, you included this in your previous email.  The problem you ran
into is I moved away from SSEC's method of installing McIDAS since I
don't think that it provides needed flexibility.  I have users unpack
the distribution tar using the script 'mcinstall'; define needed Unix
environment variables; CD to the ~mcidas/mcidas2003/src directory; and
then run make specifying the VENDOR= setting on the make invocation
line if they are not using vendor-supplied compilers.  To me this makes
more sense than hiding the build process inside a script.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.