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

[LDM #GQJ-707717]: LDM Compile Issue

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 #GQJ-707717]: LDM Compile Issue
  • Date: Fri, 03 Feb 2017 12:41:40 -0700
Justin,

> It seems I am still getting the error. I double checked and the parser header 
> file is available and located at /usr/include/libxml2/libxml/parser.h.
> 
> This is my configure line.
> 
> ./configure --enable-loggin=local0 --with-noaaport --with-gribinsert 
> --with-ulog CPPFLAGS=‘I/usr/include/libxml2/libxml’

1. The "--enable-logging" option is misspelled and superfluous;
2. The CPPFLAGS option argument is missing a minus sign; and
3. Your pathname is one directory too long.

Try this:

    /configure --with-noaaport --with-gribinsert --with-ulog 
CPPFLAGS=-I/usr/include/libxml2

> It seems I am still getting the error. I double checked and the parser header 
> file is available and located at /usr/include/libxml2/libxml/parser.h.
> 
> This is my configure line.
> 
> ./configure --enable-loggin=local0 --with-noaaport --with-gribinsert 
> --with-ulog CPPFLAGS=‘I/usr/include/libxml2/libxml’

> It appears the PNG devel libraries were not installed.

You'll have to install them. You can use the same CPPFLAGS solution if the
configure script can't find the header file.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GQJ-707717
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.