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

[McIDAS #XRR-599672]: FW: Please remove port 23 access from shu.cup.edu, and add ports 22 & 112.

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 #XRR-599672]: FW: Please remove port 23 access from shu.cup.edu, and add ports 22 & 112.
  • Date: Mon, 17 Dec 2007 10:04:53 -0700
Hi Samuel,

re:
> O.K. We're still taking with Red Hat support to see why 'yum install gcc-c++'
> doesn't work.

OK.  My experiences during the McIDAS training that I held in Brazil might
indicate that the problem might actually lie with the Fortran compiler 
environment
you are trying to use.  I ran into something similar (but not exactly the same)
in Brazil under OpenSuSE, and the problem went away when I switched from use of
g77 (which was apparently not completely/correctly installed) to gfortran.

> Are there a binary distributions of McIDAS we could use, and avoid some of 
> these issues?

No.  McIDAS is always built from source.  This eliminates a large set of 
problems
that users experience when trying to run on OSes that are not the same as the
ones available in Unidata.  For example, users have reported a range of problems
using binary distributions of GEMPAK on non-Fedora OSes like Centos (which is
essentially a freely available RedHat Enterprise WS release).  When the code is
built on the platform on which it will run, these sorts of problems (missing
shared libraries, etc.) do not occur.   Usually coming up with a working 
development
environment is very simple.

I am unsure why your lab machines are not easy to setup with a working 
development
environment.  I believe that if there was some way that you could arrange for
me to get a login to the machine having problems, I could figure out what is
really wrong and fix it (would need 'root' access to fix the problem) or develop
some sort of a workaround.

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