Re: 19990120: Compling LDM

Hiya,

There are 2 things about the install:

- the ldm.tar.Z should be unpacked in the ldm home directory. Not in the 
  ~ldm/ldm-5.0 directory.  This way the old installation doesn't get
   overwirtten. I think you probably did it correctly.


On Wed, 20 Jan 1999, Unidata Support wrote:

> >To: address@hidden
> >cc: address@hidden
> >From: address@hidden
> >Subject: Compling LDM
> >Organization: .
> >Keywords: 199901200045.RAA00229
> 
> Greetings:
> 
> Thanks for your answers regarding the versions of LDM.
> 
> I downloaded ldm.tar.Z and proceeded through the steps as outlined in
> the manual.  Everything seemed to be ok until I got the step where I
> entered "ldmadmin stop" prior to changing the value of "runtime".
> 
> I got the message:
> 
> Literal @HOSTNAME now requires backslash at ./ldmadmin line 62, within string
> Execution of ./ldmadmin aborted due to compilation errors.
> 

This error about the @HOSTNAME@, one needs to edit ldmadmin and replace
@HOSTNAME@ with the hostname of the machine.  There are online source
install instructions that covers this issue. 

http://www.unidata.ucar.edu/packages/ldm/ldmSourceInstallList.html#s7

Actually, I would review the whole document as a sanity check.

Robb...



> It was then that I discovered that the install had overwritten the binaries
> in ldm-5.0 rather than create new binaries under ldm-5.0.6.
> 
> It seems to me that I should have changed the value of runtime before
> doing the make.  Or maybe I should have defined LDMHOME more completely
> than just /usr/local/ldm as suggested.
> 
> Anyway I deleted ldm-5.0.6 and repeated the whole process so that I could
> capture the make messages.  I couldn't find any obvious compile errors
> there so I am wondering if perhaps the error from trying to run ldmadmin
> is do to the fact that is a different version than the ldm processes
> that are currently running.
> 
> I don't seem to have the source for 5.0 any more.  The previous installer
> must have deleted it or hidden it in a very safe place. :)
> 
> I am tempted to stop the ldm by hand (kill or reboot) and see if it comes 
> up.  What do you think?
> 
> I can send you the make log and the directory structure if you want. 
> 
> Assuming that the ldmadmin error is easily fixed I am assuming that ldm
> will run just fine with runtime pointing to the ldm-5.0 directory where
> all the new files seem to be.  To make things proper I could also
> copy /src over to ldm-5.0, rename ldm-5.0 to ldm-5.0.6 and rename runtime.
> 
> Right now I am most curious about the ldmadmin error.
> 
> Thanks 
> 
> Erick Lorenz, U C Davis
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================