public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nilesh Govindrajan <contact@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cryptic output from emerge
Date: Sun, 19 Feb 2012 19:54:54 +0530	[thread overview]
Message-ID: <CAPo3noa0BC3AqXqvQPaBXie=ZiMk5yQEBKRQSB38aHDc_XVRjg@mail.gmail.com> (raw)
In-Reply-To: <20120219141828.GA3038@solfire>

On Sun, Feb 19, 2012 at 7:48 PM,  <meino.cramer@gmx.de> wrote:
>
> Hi
>
> After an
>
>    emerge --color=n --newuse --update --tree --deep world -vp
>
> I got this output. What does the line with "cxx?" want say to me?
>
>
>
>    These are the packages that would be merged, in reverse order:
>
>    Calculating dependencies /
>
>    !!! Problem resolving dependencies for dev-libs/beecrypt from @selected                                                                                                                                                                     ... done!
>
>    !!! The ebuild selected to satisfy "dev-libs/beecrypt" has unmet requirements.
>    - dev-libs/beecrypt-4.2.1::gentoo USE="cxx (multilib) -doc -java -python -static-libs -threads"
>
>    The following REQUIRED_USE flag constraints are unsatisfied:
>        cxx? ( threads )
>
>    (dependency required by "@selected" [set])
>    (dependency required by "@world" [argument])
>    [1]    19260 exit 1     emerge --color=n --newuse --update --tree --deep world -vp
>
> Thank you very much in advance for a help...
>
> Best regards,
> mcc
>
>
>
>

It says you need to enable threads if you want c++ support. (If cxx
useflag is present, check for threads useflag).

-- 
Nilesh Govindarajan
http://nileshgr.com



  reply	other threads:[~2012-02-19 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 14:18 [gentoo-user] Cryptic output from emerge meino.cramer
2012-02-19 14:24 ` Nilesh Govindrajan [this message]
2012-02-19 14:25 ` Jarry
2012-02-19 14:48   ` meino.cramer
2012-02-19 14:57     ` Neil Bothwick
2012-02-19 14:56 ` Alan McKinnon

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='CAPo3noa0BC3AqXqvQPaBXie=ZiMk5yQEBKRQSB38aHDc_XVRjg@mail.gmail.com' \
    --to=contact@nileshgr.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