public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gtk+ / Cairo / pdf-flag mutual build problem.
Date: Fri, 29 Dec 2006 23:14:48 -0500	[thread overview]
Message-ID: <20061230041448.GA16591@waltdnes.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612291413080.20138@iabervon.org>

On Fri, Dec 29, 2006 at 02:23:08PM -0500, Daniel Barkalow wrote

> > Calculating dependencies... done!
> > [ebuild   R   ] x11-libs/cairo-1.2.4  USE="X png -directfb -doc -glitz
> > -svg (-pdf%)" 0 kB
> > 
> >   Oops... note the "(-pdf%)".  This option is simply not allowed for
> > Cairo on my system.  I threw in "--skipfirst" into the emerge command,
> > and it seems to be working so far.  But back to my main problem... how
> > do I reconcile gtk+ and Cairo?
> 
> Actually, the cairo ebuild now unconditionally enables pdf support; the 
> USE flag is not allowed because it is no longer possible to disable pdf 
> support. (Portage doesn't have a way to express the differences between 
> something not being a USE flag because it is unsupported and because it is 
> automatic, but if you look in the ebuild, you'll find that it's using 
> "--enable-pdf")
> 
> So gtk+ should be happy once you re-emerge cairo even without changing use 
> flags.

  So why does the flag show up at all when I do an "emerge -pv"?

-- 
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
My musings on technology and security at http://techsec.blog.ca
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-12-30  4:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-25  4:14 [gentoo-user] gtk+ / Cairo / pdf-flag mutual build problem Walter Dnes
2006-12-27 11:35 ` Mike Myers
2006-12-27 16:57   ` Dan
2006-12-29 19:23 ` Daniel Barkalow
2006-12-30  4:14   ` Walter Dnes [this message]
2006-12-30  4:21     ` Daniel Barkalow
2006-12-31  4:33       ` Walter Dnes

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=20061230041448.GA16591@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --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