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

[LDM #EIW-321327]: Updating ldm



Hi Carol,

re:
> 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?

Can you rerun the sequence of commands you ran that led to this error
capturing the output of the 'configure' and 'make install' steps into
individual log files and then send us the log files and exact sequence
of what you ran (highlight the output shown in your terminal window and
paste it into a reply)?  We need more, specific information to truly
understand what is going on.

Please refer to the instructions in:

http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/source-install-steps.html

for guidance on capturing output from 'configure' and 'make install' in to
individual log files.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


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.