From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 957EA138C48 for ; Sun, 12 Apr 2015 14:11:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A6CF2E0C3F; Sun, 12 Apr 2015 14:11:20 +0000 (UTC) Received: from mo4-p04-ob.smtp.rzone.de (mo4-p04-ob.smtp.rzone.de [81.169.146.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 639F8E08D4 for ; Sun, 12 Apr 2015 14:11:19 +0000 (UTC) X-RZG-CLASS-ID: mo04 X-RZG-AUTH: :I3kQYkG6f/ML/Lb0bAYFCBt+SpICkd7E+UrA1ycmip9RDA+sU5X/Le5mikfzMu/gLXt2 Received: from porto.localnet ([88.128.80.45]) by smtp.strato.de (RZmta 37.5 SBL|AUTH) with ESMTPSA id L059ddr3CEAxMza (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (curve sect571r1 with 571 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Sun, 12 Apr 2015 16:10:59 +0200 (CEST) From: "Andreas K. Huettel" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Machine completely broken; Ncursed! Date: Sun, 12 Apr 2015 16:13:48 +0200 User-Agent: KMail/1.13.7 (Linux/3.17.7-gentoo; KDE/4.14.6; x86_64; ; ) References: <55292E11.9040202@verizon.net> <201504112204.26649.dilfridge@gentoo.org> <5529BF6C.7090909@verizon.net> In-Reply-To: <5529BF6C.7090909@verizon.net> Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201504121614.04408.dilfridge@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Archives-Salt: 23feda80-6c2a-48d9-8633-fda3a0c0ed3a X-Archives-Hash: 9f2be31c956fa9d21cddcafa5e35cb10 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am Sonntag, 12. April 2015, 02:42:20 schrieb Alan Grimes: > > /etc/portage # emerge --info > [[: error while loading shared libraries: libtinfo.so.5: cannot open > shared object file: No such file or directory > Failed to validate a sane '/dev'. > bash process substitution doesn't work; this may be an indication of a > broken '/dev/fd'. > /etc/portage # OK. That means your system is seriously broken now, but I gather you already know that. I doubt there is a way to get back to a working system without tricks/extra downloads. Most of the comments below are now mostly "trying to find out what happened". I'm leaving out stuff where I dont see anything problematic. > > > The ncurses problem has been a low-level > > > issue for a long time but, with tinfo set, 99% of packages worked. > > > > Define low-level issue. What was broken all the time that you ignored? > > Busybox, valgrind, a number of other minor packages. OK, now what was wrong there? Do you still have any old build logs maybe? > > > 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. > > > > You're still not providing the slightest bit of useful information. > > > > What happens if you try to generate a 32bit executable? > > Fails completely due to linking errors even though it should always be > possible to compile something without its binary dependencies (with only > the headers) because symbol resolution should take place at load time. =| Well... Yes it is possible to compile things. But they also need to get linked, and for that the libraries need to be present. No you cannot build something against a library without the library being present. > CFLAGS="-O3 -march=native -pipe " > CXXFLAGS="${CFLAGS}" - -O3 is not a good idea. -O2 is safe. > LDFLAGS="-lncurses " I hope you forced that in only at the end when things were already broken and you tried to fix them. Wrong. Bad. Wrong. Bad. > ACCEPT_KEYWORDS="amd64 ~amd64" Should not be a big problem (since ~amd64 is pretty well maintained these days), but in general you'll likely hit more bugs if you run unstable. In this case it's definitely an advantage if you are familiar with bug reporting procedures and frequent our bugzilla. > USE="... > c++0x No. Just no, since you may run into all sorts of trouble with C++ programs. (There was a news item about this recently.) I doubt that it is related to your problems though. > custom-cflags No. Again. Just no. Do this and you get to keep the pieces. I dont dare to do that myself. Especially in combination with -O3 it's, well,... > discouraged Read it and despair. > sse2 sse3 sse4 Unproblematic but outdated. Also a recent news item. So, now about getting back to a working system. There are many ways, none of them really 100% clean given the amount of breakage, and I'm not really a specialist. Some ideas, unverified and untested; I've never done this myself. * Boot from a rescue system * Mount your gentoo installation somewhere * Copy your setup (/etc, /var/lib/portage/world) to a safe place (usb stick) * For an amd64 multilib system doublecheck that both in /usr and / the "lib" entry is a symlink to "lib64" in the same directory. * Download the newest amd64 multilib stage3 and untar it over your system. * restore your make.conf, *sanitized* CFLAGS="-march=native -O2 -pipe" * chroot into the system, and run emerge -eav system * then reboot normally and run emerge -eav world (you may have to repeat this a few times, since some packages may still be broken and portage won't necessarily rebuild them in the correct order) * then restore your old world file and repeat the last step IF YOU HAVE A SPARE PARTITION, there is a much better way- do a new install there, instead of all the above steps. Good luck. - -- Andreas K. Huettel Gentoo Linux developer (council, perl, libreoffice) dilfridge@gentoo.org http://www.akhuettel.de/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJVKn2dAAoJEB9VdM6hupKV2ZsP/Asgl66mmh8/Lzd0mVwNQkts GSszMvt7RNUb2k4lQetXR0psyr9Up7NDrp0plmAAguNJMtZOdgIVZsJ5sTvtWDxT 0fxM7EXD2QLzpKIUF0uQFLQ1O+68GYTK0UOai+7OzN99HwALM7U5H9k9hYIrEVY6 ZtueUazbfOgWmAM//ZPQltj4GYBeSiW9TLJUbZNHzQFqJkP+uPimYWN9QIkcGyVP UJUlU1IJP9IOF7Ing10zisK1CT3+tEXnyeU930bnaCW1rLAUcm797BmwKWZX9RfW MYqTe6jjWAmnK+n6ScAeCtcwmwZ5MeQQBD7SK8FySSpegev2dEZzrHaI9hvMajtZ 4L3i/CCwSwxUs3hjh+cn9kCb1Cs6BUqtXfR9Jt/rSZFOWVE7TbRrIssW0ZEw92x4 jKAO//H41EjK830QB6WzWLJxfYSdQ1SEaEW2WHNSdYd4vaxHv9YQp3sdm3zKxWel hY0pEJ5NtQMWGkte0XU0DgowAuDnBMn7Xac//rcOwWsSZiWIn8SmdpxvR43/xAZt Ln4k7xxJhb3a4w9Uocm3vPMOxIgRo2xFrdYNN18VGGz9zVNNyOZhECJDy9EZEtF1 liswCUhLUQMhKBau8F/DSpoL4AzZzyHciMNVVVG5PbAeYCr749KKjyp5H7zmPwhC Vbe4Ykem3g/4BnMW1+6e =AjWC -----END PGP SIGNATURE-----