public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Machine completely broken; Ncursed!
Date: Mon, 13 Apr 2015 20:55:49 -0500	[thread overview]
Message-ID: <20150413205549.275e57c5@sepulchrave.remarqs> (raw)
In-Reply-To: 552B2147.2040600@alectenharmsel.com

On Sun, 12 Apr 2015 21:52:07 -0400
Alec Ten Harmsel <alec@alectenharmsel.com> wrote:

> On 04/12/2015 09:38 PM, »Q« wrote:

> > How can I find out whether the profile is setting those variables?
> > ISTM the emerge errors I posted earlier, which happen if I get rid
> > of those variables in make.conf, indicate that they are not being
> > set at all.
> 
> You can find all the defaults here:
> /usr/portage/profiles/base/make.defaults. I don't think the KDE
> profile overrides any of the python/ruby stuff, just USE. It's
> strange that you are getting that error from util-linux; I would
> recommend getting rid of the USE_PYTHON="2.7" line from make.conf
> and, personally, avoid having so many USE flags in make.conf.

Thanks.  My /usr/portage/profiles/base/make.defaults has

PYTHON_TARGETS="python2_7 python3_3"
PYTHON_SINGLE_TARGET="python2_7"

The error message was

  The following REQUIRED_USE flag constraints are unsatisfied:
    python? ( exactly-one-of ( python_single_target_python3_3
    python_single_target_python3_4 python_single_target_python2_7 ) )

It looks to me like make.defaults sets exactly one of those.  Is it
possible my USE="-* wipes out use_expand things as well?






  reply	other threads:[~2015-04-14  1:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 14:22 [gentoo-user] Machine completely broken; Ncursed! Alan Grimes
2015-04-11 14:34 ` Neil Bothwick
2015-04-11 17:22   ` Mick
2015-04-11 19:41   ` Alan Grimes
2015-04-11 21:27     ` Neil Bothwick
2015-04-11 20:04 ` Andreas K. Huettel
2015-04-12  0:42   ` Alan Grimes
2015-04-12  0:58     ` [gentoo-user] " walt
2015-04-12  1:02     ` [gentoo-user] " Peter Humphrey
2015-04-12  1:58     ` Dale
2015-04-12  9:12     ` J. Roeleveld
2015-04-12 17:23       ` [gentoo-user] " »Q«
2015-04-12 18:35         ` Matti Nykyri
2015-04-13  1:07           ` »Q«
2015-04-13  5:48             ` Alan McKinnon
2015-04-14  2:08               ` »Q«
2015-04-12 20:07         ` J. Roeleveld
2015-04-13  1:15           ` »Q«
2015-04-13  1:24             ` Alec Ten Harmsel
2015-04-13  1:38               ` »Q«
2015-04-13  1:52                 ` Alec Ten Harmsel
2015-04-14  1:55                   ` »Q« [this message]
2015-04-13  5:52                 ` Alan McKinnon
2015-04-14  3:38                   ` »Q«
2015-04-13  7:51                 ` Neil Bothwick
2015-04-14  3:51                   ` »Q«
2015-04-14  7:47                     ` Neil Bothwick
2015-04-15  3:09                       ` »Q«
2015-04-15  8:24                         ` Neil Bothwick
2015-04-12  9:31     ` [gentoo-user] " Neil Bothwick
2015-04-12 14:13     ` Andreas K. Huettel
2015-04-11 23:23 ` Fernando Rodriguez
2015-04-12  1:25   ` Alan Grimes
2015-04-12  0:06 ` Peter Humphrey
2015-04-12  1:27   ` Alan Grimes
2015-04-12 14:52     ` Peter Humphrey
2015-04-16  2:40 ` Fernando Rodriguez

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=20150413205549.275e57c5@sepulchrave.remarqs \
    --to=boxcars@gmx.net \
    --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