From: "Jörg Schaible" <Joerg.Schaible@Elsag-Solutions.com>
To: <cygwin@cygwin.com>
Subject: FW: Libxml2 package problem?
Date: Wed, 27 Aug 2003 10:23:00 -0000 [thread overview]
Message-ID: <F0D7281DAB048B438E8F5EC4ECEFBDDC174E2A@esmail> (raw)
Hi,
sorry for wrong alarm. I realized, that configure is writing a log file and I detected that it misses the development environment for libiconv. Installed that and building succeeds without any problem.
Regards,
Jörg
-----Original Message-----
From: Jörg Schaible
Sent: Wednesday, August 27, 2003 11:22 AM
To: cygwin@cygwin.com
Subject: Libxml2 package problem?
Hello libxml2 maintainer,
currently I try to compile davtool-0.1.0 (http://sourceforge.net/projects/davtool), a command line utulity I would expect to build OOTB on Cygwin. Unfortunately the configuring fails due to an unfound parser.h in the xml-package, see output:
========== snip =============
checking for xml2-config... xml2-config
checking libxml/xmlversion.h usability... yes
checking libxml/xmlversion.h presence... yes
checking for libxml/xmlversion.h... yes
checking libxml/parser.h usability... no
checking libxml/parser.h presence... no
checking for libxml/parser.h... no
checking parser.h usability... no
checking parser.h presence... no
checking for parser.h... no
configure: error: could not find parser.h, libxml installation problem?
[1] jos@JOS /usr/local/src/davtool-0.1.0
$ find /usr -name "parser.h" /usr/include/libxml2/libxml/parser.h
========== snap =============
Configure expects this file obviously in /usr/include/libxml and I am asking myself if this is a problem of the libxml2 package installing files at the wrong position or not including a necessary link?
Regards,
Jörg
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
reply other threads:[~2003-08-27 9:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F0D7281DAB048B438E8F5EC4ECEFBDDC174E2A@esmail \
--to=joerg.schaible@elsag-solutions.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).