From: Alan Grimes <ALONZOTG@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Machine completely broken; Ncursed!
Date: Sat, 11 Apr 2015 10:22:09 -0400 [thread overview]
Message-ID: <55292E11.9040202@verizon.net> (raw)
My machine is so completely broken right now I can't open any new
terminal sessions.
This is because I stupidly tried to toggle tinfo useflag in a desperate
attempt to get everything in my portage tree working again.
Why now did nothing in my portage tree build?
It wasn't building for two reasons:
1. My machine is not correctly configured to build 32 bit executables,
mainly because I cannot find a 32 bit version of ncurses that ld is
willing to acknowledge the existence of.
2. LD cannot find ncurses, -- It simply can't, in 64 bit mode either.
That is the only error message it ever gives and vast amount of effort
spent in sessions over the last year and a half have failed to find any
solution. I only installed Gentoo on this machine four and a half years
ago so it's hard to imagine what could have gotten this royally foobar
in such a short period.
I am an enthuseastic supporter of multilib, I even tried to set it up
myself but failed due, once again, to ncurses.
I was running my system as usual, running updates every week or two, no
major issues since the libav clusterfuck a few months ago. (Libav is a
cult not a software project). The ncurses problem has been a low-level
issue for a long time but, with tinfo set, 99% of packages worked.
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. =( I tried the no-multilib profile but it didn't have a
number of essential useflags and was foobar.
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 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.
--
IQ is a measure of how stupid you feel.
Powers are not rights.
next reply other threads:[~2015-04-11 14:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 14:22 Alan Grimes [this message]
2015-04-11 14:34 ` [gentoo-user] Machine completely broken; Ncursed! 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«
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=55292E11.9040202@verizon.net \
--to=alonzotg@verizon.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