19990814: mcidas 7.6 install problems

>From: address@hidden
>Organization: SMSU
>Keywords: 199908122231.QAA22964 McIDAS-X,-XCD 7.60

Bill,

>Well, I got more problems for you.  Let's work in descending
>order:
>
>Here is the output from attempted install:
>cirrus:/home/mcidas/mcidas7.6/src> make install.mcxall
>        cd /home/mcidas/bin && rm -f cal_init  disable_mcidas_gui  enable_mcid
>as_gui  fx  mcidas  mcidasx  mcservsh  ./mcar  ./mccomp  ./tclcomp  ./mcfc  ./
>mcln  ./mclog  nav_init  xrefit
>        cd /home/mcidas/bin && rm -f ./convdlm  ./mcmkhelp
>make: ERROR: Lack files needed for install: mcimage
>
>You must do a 'make' before doing a 'make install'
>
>make: 1254-004 The error code from the last command is 1.
>
>Stop.

OK, mcimage was not built, and the link failure is not propagating back
to make so that it would fail like it should.

>I've tried a couple of clean makes (even re-ftped), tried make mcimage,
>checked the LD_LIBRARY_PATH/LIBPATH issue....no joy.

We need to look in ~mcidas/mcidas7.6/src/makelog for the mcimage build/load
and find out exactly why/how it is failing.

One quick question, however.  How were you able to bring up a session for
testing if mcimage had not been made before?  Perhaps your earlier test
session was using a mcimage from 7.4?

>So, now I just did a make mcimage...it compiled a few dozen programs,
>last few lines:
>compile nv1tiro.f:              done
>compile nv2tiro.f:              done
>update  libmcidas.a:            done
>link    mcimage:                done

But the mcimage link probably failed.

>now:
>
>irrus:/home/mcidas/mcidas7.6/src> make install.mcxall
>        cd /home/mcidas/bin && rm -f cal_init  disable_mcidas_gui  enable_mcid
>as_gui  fx  mcidas  mcidasx  mcservsh  ./mcar  ./mccomp  ./tclcomp  ./mcfc  ./
>mcln  ./mclog  nav_init  xrefit
>        cd /home/mcidas/bin && rm -f ./convdlm  ./mcmkhelp
>make: ERROR: Lack files needed for install: mcimage
>
>You must do a 'make' before doing a 'make install'
>
>make: 1254-004 The error code from the last command is 1.
>Stop.

Ditto from above.  What does makelog say about why the link failed?

>So, that's where I currently am.

Please let me see the makelog entry for mcimage so I can figure out
what is going on (and/or give me the mcidas login).

>AT this point I have shut down ldm and the crontab jobs that run
>our mcidas sessions, because trying to test 7.6 with batch jobs
>being initiated was just not feasible

OK.  If you had not uninstalled 7.4, and had not installed 7.6, then
your testing would be non-invasive.

>....but now it seems testing
>is impossible....if I start it up for a test the small initial
>window with the slider going back and forth stays forever...

That widget is waiting until mcimage starts.  With no mcimage, the
slider will keep going forever just as you note.

>it
>looks like it is trying to run the skedfile stuff, but maybe
>there's no data or connections to anything.

It is likely that your scheduler is being started through an entry
in your ~mcidas/.mcidasrc file.  If you did not install 7.6 (and
you shouldn't have since the build and test did not succeed 100%),
then 7.4 applications would still be used for your automated LDM
things.

>So we are totally dead in the water....

This is bad.  Again, if you did not do the 'make install.xxxx' then
your 7.4 stuff should still be working, and you should only be
dead in the water as far as 7.6 is concerned (this is the reason
for the test step).

>At any rate...by this time you will have addressed all my questions,
>but my first priority here is just to get the new release installed.

OK.  I am ready to help in any way I can.

>We'll deal with system vagaries, shell issues, XCD, ADDE, and testing
>once we get it installed.

OK.

>Thanks again for all your help.

Let's get to the bottom of the mcimage link failure first.  After that,
we can see if the graphics test that you reported first goes away or
is still there (I imagine it will disappear).  Please send the
section on the mcimage build/link from ~mcidas/mcidas7.6/src/makelog
so I can see what is happening.  The most likely thing is that some
library is not being found in the link step.

Tom