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

[LDM #EIW-321327]: Updating ldm

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: [LDM #EIW-321327]: Updating ldm
  • Date: Fri, 15 Jul 2016 11:26:06 -0600
Carol,

This reply is for a couple of emails ago.

The configure-script's "--enable-logging=..." option should only be used if you 
intend to use the system logging daemon for logging. If you don't specify the 
configure-scripts's "--with-ulog" option, then the system logging daemon won't 
be used.

IF used, the "--enable-logging=..." option takes an argument that specifies the 
facility that LDM programs will use when they send log messages to the system 
logging daemon. Valid arguments are "local0", "local1", "local2", ..., 
"local7". The default if the option isn't specified is "local0".

> So after making sure that the new version of ldm was running properly on
> fog.ssec.wisc.edu, I've decided to try and install it on 4 other
> machines. Now I'm working on amrc.ssec.wisc.edu.
> 
> When running the configure
> 
> './configure --enable-logging'
> 
> I'm getting the following error 'configure: error: Header-file not
> found'. Then I don't think the make install is working correctly and I
> get the following when I try to do the root stuff 'make: *** No rule to
> make target `root-actions'.  Stop.'
> 
> Any ideas? Maybe I'm unpacking the download file incorrectly?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: EIW-321327
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.