From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org, gentoo-user@gentoo.org
Subject: [gentoo-dev] libxml/libxml2 problems.
Date: Sat Nov 10 07:00:03 2001 [thread overview]
Message-ID: <1005400727.3244.4.camel@zoidberg> (raw)
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
Hi!
I've now tracked down the problem (thanks alpha for having the problem
:)
The problem was that libxml2 just recently changed to install in
/usr/include/libxml2/libxml instead of /usr/include/libxml. This
resulted in apps changing there includes from
#include <gnome-xml/libxml.h>
to
#include <libxml/libxml.h>
and controlling which libxml to use from configure by either calling
xml-config --cflags
or
xml2-config --cflags
so if you had an old libxml2 (libxml2 2.4.41 was doing wrong at least)
that resulted in the makefile finding /usr/include/libxml before
/usr/include/gnome-xml/libxml (which it should).
So, the fix, unmerge all old versions of libxml2 and remerge libxml2
>2.4.9
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2001-11-10 13:59 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=1005400727.3244.4.camel@zoidberg \
--to=hallski@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@gentoo.org \
/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