From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads up: gtk-doc-1.18 build failure...
Date: Sun, 23 Oct 2011 10:47:14 -0400 [thread overview]
Message-ID: <CA+czFiDO1B4APg=ez+whn_9wFkTgq5zbZFPziXNH-WWUUxN5Uw@mail.gmail.com> (raw)
In-Reply-To: <4EA4249D.3020807@coolmail.se>
On Sun, Oct 23, 2011 at 10:28 AM, pk <peterk2@coolmail.se> wrote:
> Hi,
>
> If anyone encounters issues with building gtk-doc-1.18 (needed for gimp
> "doc" USE flag, amongst others) you need to have the "python" flag
> enabled for the libxml2 package in order to build gtk-doc (the gtk-doc
> fails to build due to not finding libxml2 module [which I assume is a
> python one]). I guess this is related to the "python" USE flag removal
> in the profiles...
File a bug report; it sounds like gtk-doc's ebuild isn't declaring a
dependency on libxml2 having the 'python' USE flag. emerge should have
told you, "hey, the following USE flag changes are needed..."
--
:wq
next prev parent reply other threads:[~2011-10-23 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 14:28 [gentoo-user] Heads up: gtk-doc-1.18 build failure pk
2011-10-23 14:47 ` Michael Mol [this message]
2011-10-23 14:47 ` Michael Orlitzky
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='CA+czFiDO1B4APg=ez+whn_9wFkTgq5zbZFPziXNH-WWUUxN5Uw@mail.gmail.com' \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.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