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

20011128: McIDAS vis-a-via Solaris 7/8 (cont.)

>From: "James R. Frysinger" <address@hidden>
>Organization: College of Charleston
>Keywords: 200111061842.fA6Igt112242 LDM binary install


re building from source
>Well, that was a bit of an educational exercise! Grin. I had to add a 
>couple of directories to my ldm .cshrc path and had to setenv PERL 

Sounds reasonable.

>That got me as far as make install_setuids (while su'd to 

This should have been done after you did:

setenv LDMHOME /usr/local/ldm
cd ~ldm/ldm-5.1.4/src
make install

The ./configure step creates a Makefile that has things like CC
defined in it.

>Root, of course, has a very limited path so I had to provide the 
>full path for make. But then, cc failed because cc could not be found. 

Hmm...  I am suprised by this.  CC is the macro that gets set for the C
compiler to use.  Since you are using gcc, this could have been set to
be a simple 'gcc' or the fully qualified pathname for gcc (e.g.,
/usr/local/bin/gcc or something else).  The latter definition would
allow make to be run as 'root' and succeed even though 'root's PATH did
not include the directory where gcc lives.

>To fix that I would probably have to find out where it was expected and 
>to provide a link to the actual location or I would have to modify the 

Setting the CC environment variable _before_ configure is run should
be sufficient.

>So, when I get back home, I reckon I'll drop back 10 m and punt. The 
>source was ldm-5.1.4 and the binary is ldm-5.1.2. I'll re-download the 
>source binary and install that. That won't be until this weekend, at 
>the earliest. The slight difference in version numbers is not a big 
>blip on my radar screen.

Since you already have time invested in the procedure, I would get the
build to work.

>By the way, before I altered the directories .../mcdata/ldm/data and 
>.../mcdata/ldm/logs and tried compiling the source code, I tested the 
>binary installation with ldmadmin start (& stop) and it had no 

OK, good.

>It's fussing now because I've scrambled things a bit....

This is not suprising.

>re: notifyme
>It worked! We are indeed "hooked up". Dang, it felt good seeing those 
>data file headers rolling in......

What notifyme running successfully tells you is:

o the upstream host is allowing you to ask for data
o you can see when it receives data from its upstream host

The latter bit of information is _very_ useful.  If your system is
not ingesting data (sometime in the future, this comment is for
future use), you can see if your upstream site is getting data.
If it is, the problem is on your end.  If it is not, then the problem
is elsewhere and you should contact the site representative at the
upstream host to let him/her know that there is some sort of a problem.
The slowest thing to do at a point like that is contact Unidata
support.  It is always better/quicker to work with the site(s) that
are feeding you data.
>I got an email this morning promising that ports 500 and 503 would be 
>opened by 0900 LT. Wanna give it a whirl again?

It works!  I did the following to verify this:

        Dataset Names of Type: IMAGE in Group: RTIMAGES

Name         NumPos   Content
------------ ------   --------------------------------------
ANTARCTIC       10    Antarctic IR Composite
EDFLOATER-I     10    Educational Floater
EDFLOATER-II    10    Educational Floater II
GE-IR           10    GOES-East North America IR
GE-IRTOPO       10    GOES-East IR/TOPO Composite
GE-VIS          10    GOES-East North America VIS
GE-VISTOPO      10    GOES-East VIS/TOPO Composite
GE-WV           10    GOES-East North America H2O
GEW-IR          10    GOES-East/West IR Composite
GEW-IRTOPO      10    GOES-East/West IR/TOPO Composite
GEW-VIS         10    GOES-East/West VIS Composite
GEW-VISTOPO     10    GOES-East/West VIS/TOPO Composite
GEW-WV          10    GOES-East/West H2O Composite
GW-IR           10    GOES-West Western US IR
GW-IRTOPO       10    GOES-West IR/TOPO Composite
GW-VIS          10    GOES-West Western US VIS
GW-VISTOPO      10    GOES-West VIS/TOPO Composite
GW-WV           10    GOES-West Western US H2O
MDR             10    Manually Digitized Radar
MDRTOPO         10    MDR/TOPO Composite
MOLL-IR         10    Mollweide Composite IR
MOLL-IRTOPO     10    Mollweide IR/TOPO Composite
MOLL-WV         10    Mollweide Composite H2O
RESFLOATER      10    Research Floater

DSINFO -- done

So, I can read from your remote ADDE server.  Now all you need is the

>Talk to you when I get back, Tom.

OK, things are looking good.


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.