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

20040805: LDM 6.0.14 installation Help (cont.)

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: 20040805: LDM 6.0.14 installation Help (cont.)
  • Date: Thu, 05 Aug 2004 19:55:26 -0600
>From: mynul khan <address@hidden>
>Organization: St. Cloud State
>Keywords: 200408050000.i7500GaW005480 LDM build

Mynul,

>First of all, thank you very much for your prompt
>reply yesterday.

No worries.

>Today I resumed where I left of
>yesterday. I followed your instructions and seems we
>avoided the problems that we had earlier. But still we
>have more fatal errors in make.log. 
>I would very much appreciate if you could help me out
>with this.
>By the way, I work for Earth and Atmospheric Science
>Dept. at St. Cloud State University.

Since you work for St. Cloud State, and since St. Cloud State
is not a major IDD relay node, there is no reason that you
need to build the LDM with large (> 2 GB) queue support.
Give this, I advise that you do the following:

1) undefine all relevant defines in the environment in which
   you are building the LDM (i.e., CFLAGS, CPPFLAGS, LIBS,
   etc.)

2) remove the entire ~ldm/ldm-6.0.14 directory tree and start
   a bulid from scratch:

cd ~ldm
zcat ldm-6.0.14.tar.Z | tar xvf -
cd ldm-6.0.14/src
./configure
make
make install
sudo make install_setuids

The only problem you could run into is if your development
environment is non standard.

>Thank you,
>-Mynul

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.