From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Machine completely broken; Ncursed!
Date: Sat, 11 Apr 2015 18:22:53 +0100 [thread overview]
Message-ID: <201504111823.02666.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20150411153410.3edb13c9@digimed.co.uk>
[-- Attachment #1: Type: Text/Plain, Size: 1599 bytes --]
On Saturday 11 Apr 2015 15:34:10 Neil Bothwick wrote:
> On Sat, 11 Apr 2015 10:22:09 -0400, Alan Grimes wrote:
> > And then portage did two things.
> >
> > 1. It masked emul-linux -- A move that I support, it's time to see that
> > go.
> >
> > 2. It sent out a profile that sets variable ABI_x86 with 32 bit enabled.
> > ALARM: ABI_x86 should be set in exactly one place:
> > /etc/portage/make.conf and nowhere else. But, nevertheless, ABI_x86 WAS
> > set which broke the profile because my system cannot compile 32 bit
> > executables.
>
> That seems odd, I use several 64 bit profiles here and all of them have
> ABI_X86="64"
Same here, but I do not have it explicitly specified it in make.conf.
> > Right now my system is completely unusable and will need fresh stage3
> > packages followed by an emerge emptytree to recover. But before I can do
> > that, I need a sane profile
>
> Can't you just set ABI_X86="64 -32" in make.conf?
Is it even needed at all?
If there are packages that require 32bit libs portage will ask for it, yes?
> > and to know that the person who pushed out
> > the changes to portage, obviously without any testing whatsoever, that
> > broke my system so comprehensively is tortured, executed, butchered, and
> > then cremated.
>
> That's quite lenient, you could have left the execution until
> last :)
Cremation will not leave a long lasting impression in dev circles, but first I
suggest that you check the problem is not caused by something entirely
different to the change in emul-linux.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-04-11 17:23 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 [this message]
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«
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=201504111823.02666.michaelkintzios@gmail.com \
--to=michaelkintzios@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