From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KlgeF-0004V1-NC for garchives@archives.gentoo.org; Fri, 03 Oct 2008 09:08:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3CFBEE0343; Fri, 3 Oct 2008 09:08:31 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by pigeon.gentoo.org (Postfix) with ESMTP id DFE57E0343 for ; Fri, 3 Oct 2008 09:08:30 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Klge4-0003v4-HZ for gentoo-amd64@lists.gentoo.org; Fri, 03 Oct 2008 09:08:20 +0000 Received: from ip68-231-12-43.ph.ph.cox.net ([68.231.12.43]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Oct 2008 09:08:20 +0000 Received: from 1i5t5.duncan by ip68-231-12-43.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Oct 2008 09:08:20 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Problems customizing gentoo Date: Fri, 3 Oct 2008 09:08:02 +0000 (UTC) Message-ID: References: <200810022135.m92LZ3fY022723@raven.ontheside.net> <200810021942.45089.rick@aofh.us> <19351.0605059148$1222999100@news.gmane.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-12-43.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: a7cf9dea-b6f0-496a-a270-0c5401b8a8df X-Archives-Hash: cf19afff0cd1d6ce16d91e5506d4545e Drake Donahue posted 19351.0605059148$1222999100@news.gmane.org, excerpted below, on Thu, 02 Oct 2008 21:56:58 -0400: > TRY using 2008.0 minimal livecd following the handbook in detail as > though you were a gentoo first timer. A lot of knowledge is also a > dangerous thing. Good advice! =3D:^) First, note that stage-1 installs are no longer supported, due to nasty=20 circular dependency issues that are very difficult to work out. They're=20 still provided and in theory can still work, but the decision was that it= =20 was simply too much trouble trying to support stage-1, given that the=20 same customized end result can be achieved by starting from a stage-3,=20 remerging system, then world. The caveat there is that one or more=20 packages may need to be done out of order, if the USE flags changed=20 significantly from the defaults for that stage-3. As for the glibc errors, what this type of glibc errors usually mean is=20 that somewhere along the line your multilib config got screwed up, and=20 gcc can no longer compile one of 32-bit or 64-bit correctly. There's a=20 number of different ways the multilib could have gotten screwed, and it's= =20 often not worth the trouble to figure out which it was, but just to fix=20 it, by starting from a stage-3 once again. Actually, it's often possible= =20 to fix the problem by remerging just one package, gcc, from the stage-3=20 (quickpkg it to a binpkg, then emerge -K the binpkg). However, just=20 doing the full stage-3 should work as well and is more likely to fix=20 other misc errors. FWIW, after losing 32-bit compiling several times, I got tired of it and=20 went to the no-multilib profile, which then kills the 32-bit bits of=20 gcc/glibc/binutils/sandbox. The biggest reason for multilib is legacy=20 support of 32-bit-only closed source packages. Since they're closed=20 source, porting them to 64-bit isn't an option (the major open source=20 stuff has all long been ported, OpenOffice was one of the last open=20 source apps not ported, and it is now), and 32-bit compatibility must be=20 maintained if you use them. Since I don't do closed source (in general,=20 I couldn't legally do so even if I wanted to, since I no longer agree to=20 sign my rights away nor will I accept their disclaimer for damages when=20 it's a black-box who /knows/ what's in), there's very little reason I'd=20 ever need 32-bit, and avoiding all the hassles that come with multilib=20 has been a MUCH better choice for me. =20 Of course, even with no-multilib, if I needed to do 32-bit compiles as I=20 now do since I just got an Acer Aspire One AOA-150L netbook and plan on=20 putting Gentoo on it, with the work done on my main 64-bit no-multilib=20 system, it's still very possible to install an x86 (32-bit) stage into a=20 chroot and build a full 32-bit system from there. That's actually what=20 I'll be doing, running a full 32-bit chroot with FEATURES=3Dbuildpkg, the= n=20 installing the binary packages on my AA1 netbook. So if you can do without multilib, do consider switching to the no- multilb profile. It has certainly simplified my life here, and as a=20 bonus, gcc and glibc only take half the time to merge, because they only=20 build for a single bitness instead of two. Given that both those=20 packages are fairly major and take a decent amount of time to build,=20 halving that time is nice! --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman