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

[LDM #OSN-166203]: FW: Cumulus Server: LDM


> FYI - Can you help with this?
> Thanks!
> Steven
> ________________________________
> From: Jashelle Ojeda address@hidden
> Sent: Tuesday, July 10, 2012 8:49 AM
> To: Steven Lazarus; Michael Splitt
> Cc: Eric Gerard
> Subject: Cumulus Server: LDM
> I'm trying to install LDM but I keep getting this error. I'm not sure what it 
> means, but maybe you have encountered it before.
> Error:
> Making install in feedme
> make[1]: Entering directory `/usr/local/ldm/ldm-6.10.1/src/feedme'
> depbase=`echo feedme.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> gcc -DHAVE_CONFIG_H -I. -I..   -I../ulog -I../protocol -I../misc -I..  -g -O2 
> -MT feedme.o -MD -MP -MF $depbase.Tpo -c -o feedme.o feedme.c &&\
> mv -f $depbase.Tpo $depbase.Po
> feedme.c: In function âmainâ:
> feedme.c:467: error: âLOG_LOCALNâ undeclared (first use in this function)
> feedme.c:467: error: (Each undeclared identifier is reported only once
> feedme.c:467: error: for each function it appears in.)
> make[1]: *** [feedme.o] Error 1
> make[1]: Leaving directory `/usr/local/ldm/ldm-6.10.1/src/feedme'
> make: *** [install-recursive] Error 1

I suspect that the configure(1) script was invoked like "configure 
--enable-logging=log_localn ..." rather than like "configure 

The LDM user should go into the top-level source-directory and execute the 
command "make distclean" and then re-execute the configure(1) script (with a 
proper value for the "--enable-logging" option) and then build the LDM package.

> I can see that the directory does not exist. If I were to build it, I'm not 
> sure what would go in the file.
> --
> Jashelle Ojeda
> Vice President of Phi Sigma Sigma, Iota Eta
> Vice President of American Society of Civil Engineers-FIT
> Treasurer of GSA
> President of Blue Wave Flag Football
> B.S. in Ocean Engineering

Steve Emmerson

Ticket Details
Ticket ID: OSN-166203
Department: Support LDM
Priority: Normal
Status: Closed

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