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

20021031: LDM upgrade error messages

>From: "Benjamin Cotton" <address@hidden>
>Organization: Purdue
>Keywords: 200210311528.g9VFSLX21227 LDM 5.2.1

Ben,

>I finally got around to building LDM 5.2.1 on Purdue's machine (no idea
>when it will be operational yet, as our sysadmin seems to have vanished
>behind a wall of Mountain Dew cans) and I get the following error
>messages when I type % make install
> 
>(anvil.eas.purdue.edu) [/project/ldm/ldm-5.2.1/src]% make install
>mkdir /net/anvil/project/ldm/ldm-5.2.1/bin
>mkdir /net/anvil/project/ldm/ldm-5.2.1/include
>mkdir /net/anvil/project/ldm/ldm-5.2.1/lib
>mkdir /net/anvil/project/ldm/ldm-5.2.1/man
>mkdir /net/anvil/project/ldm/ldm-5.2.1/man/man1
>mkdir /net/anvil/project/ldm/ldm-5.2.1/man/man3
>cp: libldm.a: No such file or directory
>*** Error code 1 (ignored)
> 
>Making `install' in directory
>/net/anvil/project/ldm/ldm-5.2.1/src/config
> 
>updated /net/anvil/project/ldm/ldm-5.2.1/include/ldmconfig.h
> 
>Returning to directory /net/anvil/project/ldm/ldm-5.2.1/src
> 
> 
>Making `install' in directory /net/anvil/project/ldm/ldm-5.2.1/src/ulog
> 
>c89 -g -DHAVE_CONFIG_H -I../config -c  ulog.c
>c89 -g -DHAVE_CONFIG_H -I../config  hupsyslog.c   -o hupsyslog
>c89: invalid operand
>usage: c89 [-c] [-D name[=value]] [...] [-E] [-g] [-I directory ...]
>       [-L directory ...] [-o outfile] [-O] [-s] [-U name ...] operand
>...
>*** Error code 64
> 
>Stop in /net/anvil/project/ldm/ldm-5.2.1/src/ulog.
>*** Error code 1
> 
>Stop in /net/anvil/project/ldm/ldm-5.2.1/src.
>*** Error code 1
> 
>Stop in /net/anvil/project/ldm/ldm-5.2.1/src.
> 
>I was following the instructions on the website.  I know some errors are
>to be expected with any program and many times they are there just to
>torment the programmers.  Are these messages ignorable, or do I need to
>unbreak something?

Try the following:

cd ldm-5.2.1/src
make distclean
setenv CC cc              <- uses appropriate syntax for your Unix SHELL
./configure
make
make install
...

Tom Yoksas


>From address@hidden Fri Oct 25 10:58:33 2002
>To: <address@hidden>
>Subject: LDM on BSD
>Date: Fri, 25 Oct 2002 16:56:09 -0000

Hi,
 
Due to the incredible load on our department sysadmin, we have yet to
upgrade to LDM 5.2 here at Purdue.  We are still running LDM 5.1.3, with
only a few issues.  The first being 'ldmadmin newlog' not doing quite
what I expect.  I have a crontab set up to run 'ldmadmin newlog' every
evening, but when I look at the logs, there are commonly two to three
days worth of material in each file.  Also, the file ldmd.log is always
at size 0.  ldmd.log.1 thru ldmd.log.4 are correct (excepting the
multiple days).  The second issue is old stats files in my logs
directory are not always being deleted once the stats have been sent in.
Sometimes they are, sometimes they aren't.with no particular pattern
that I've seen.
 
The general suspicion is that this in an OS issue.  We run on FreeBSD,
which last I knew is not supported by Unidata.  Are there any plans to
support BSD in the future?  If not, what other sites run FreeBSD so we
can handle OS-related questions for each other.  I'm pretty sure Jim
Koermer at Plymouth State is running BSD, but he is the only one I know
of.
 
One last thing.on the LDM site logs page  (part of the IDD pages), the
link to Purdue's site logs is rather outdated.  I have made a new
webpage for our LDM www.eas.purdue.edu/ldm and the logs specifically can
be found at www.eas.purdue.edu/ldm/logs.html
 
Thank you,
Ben
 
===================================================
Benjamin J. Cotton
LDM/Forecast Game Administrator
Department of Earth and Atmospheric Science,
Purdue University
 
165 Cary Quadrangle                         cell: (502) 551-5403
West Lafayette, IN  47906         campus: (765) 49-52298
 
address@hidden                     www.eas.purdue.edu/ldm
www.eas.purdue.edu/~bcotton           www.eas.purdue.edu/forecast