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

Re: 20010706: LDM under Redhat 6.2

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: Re: 20010706: LDM under Redhat 6.2
  • Date: Fri, 06 Jul 2001 12:35:17 -0600
Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >From: "James Hayes" <address@hidden>
> >Subject: LDM under Redhat 6.2
> >Organization: NWS Gray ME
> >Keywords: 200107060655.f666tp104430 LDM RedHat 6.2 Linux
> 
> Hi,
> 
> Here at the NWS Forecast Office in Gray, ME, we recently upgraded the
> OS on the machine running LDM 5.0.9.  Previously, we had Slackware 7.0
> running LDM 5.0.9 with no problems.
> 
> After upgrading the OS to RedHat 6.2, pqact no longer runs.  I compiled
> LDM 5.0.9 from the source under RedHat 6.2, but pqact still would not
> launch.  Running pqact by hand yielded the following:
> 
> "cannot load libgdbm.so.1"
> 
> Is there something in the compilation that I missed?
> 
> Thanks,
> 
> Jim Hayes
> NWS Gray ME
> 
> ------- End of Forwarded Message

Hi Jim,

Good detective work!  pqact is looking for the gdbm shared library.  On
my RedHat 7.0 machine that library exists in /usr/lib.  Apparently it's
missing in your new installation, or maybe it's in some nonstandard
place.  

Assuming it's missing, if you want to use the gdbm you'll need to get
the library from somewhere.  It may be on your installation disk.  If
you don't want to use gdbm, then go to ~ldm/src/pqact and change one
line in the Makefile.  Change

DEFINES =  -DHAVE_CONFIG_H to
DEFINES =  -DHAVE_CONFIG_H -DNO_DB

Then remove *.o in that directory and do 'make pqact'.  This will build
pqact without the interface to gdbm.  But, if you do this you will need
to do the same every time you upgrade your ldm.

Btw, since you're upgrading, why don't you grab the latest version of
the ldm?  We're currently on V5.1.4.  The changes in 5.1.2 were
significant - I recommend you get them.

Please let me know if this solves your problem.

Anne




-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************