Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install
On Fri, Jun 25, 2010 at 12:44:47AM -0500, Dale wrote For future reference, after you switch gcc, you should run env-update and source /etc/profile. Then you don't have to log out and back in again. One could argue that one is easier than the other tho. ;-) I knew I had to do a couple of things if I wanted to avoid logout and login, but I couldn't remember off the top of my head. It was easier to just log out+in rather than look it up. -- Walter Dnes waltd...@waltdnes.org
Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install
Walter Dnes writes: On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote I'll repeat the advice I was given in this list sometime around last Christmas (but can't find the thread now): you're bound to find some pesky application which is only available in 32bit and then you'll curse for having to reinstall. If anything, I'll install a VM to run it in. I'm curious. Are there advantages on not running a multilib profile? RANT Why on earth will xorg-x11 *NOT* build if I mask out various arabic, cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a kiosk machine at UN headquarters fer-cryin-out-loud. /RANT xorg-x11 depends on them, I think there is no way to tell portage a dependency is optional. Might be nice feature, though. Debian has something like this I think, 'suggested packages' that may be installed additionally if desired. Maybe an 'optional' use flag could do this? But it would habe to be set for every package, not in the DEPEND list in the xorg-x11 ebuild. A DEPEND_IF_NOT_MASKED entry in the ebuild would be nice. Anyway, I do not install xorg-x11 at all, but xorg-server instead. Which means I have to care about optional stuff for myself, like fonts, tools like xdpyinfo and such. But at least I do not have cyrillic fonts on my system :) Wonko
Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install
On Thu, 24 Jun 2010 23:29:09 -0400, Walter Dnes wrote: RANT Why on earth will xorg-x11 *NOT* build if I mask out various arabic, cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a kiosk machine at UN headquarters fer-cryin-out-loud. /RANT Because xorg-x11 is metapackage that pulls everything in. If you want to choose what is installed, either emerge components individually or create a set. -- Neil Bothwick Copy from another: plagiarism. Copy from many: research. signature.asc Description: PGP signature
[gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install
On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote I'll repeat the advice I was given in this list sometime around last Christmas (but can't find the thread now): you're bound to find some pesky application which is only available in 32bit and then you'll curse for having to reinstall. If anything, I'll install a VM to run it in. Have you tried setting -j1 and trying emerging it once more? I *ALWAYS* have -j1 in /etc/make.conf. Anyways, it turned out to be something completely different. Whilst doing additional Google searching, I stumbled across Foolproof Gentoo World Update Build Order at http://foxpa.ws/tag/package-keywords/ and it was proof against this fool, too G. My problem was that the Gentoo install snapshot put in gcc-4.3.4, and emerge --update world pulled in gcc-4.4.3-r2. So far, so good. But after the first build, I forgot to gcc-config over to 4.4.3-r2 ... dohhh. Anyhow, after switching over, rebuilding gcc-4.4.3-r2, exiting, logging back in, unmerging gcc-4.3.4, and rebuilding glibc, I successfully emerged system and world. I'm now emerging xorg-x11. RANT Why on earth will xorg-x11 *NOT* build if I mask out various arabic, cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a kiosk machine at UN headquarters fer-cryin-out-loud. /RANT -- Walter Dnes waltd...@waltdnes.org
Re: [gentoo-user] [SOLVED] gcc build fails during emerge system on new 64-bit install
Walter Dnes wrote: On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote I'll repeat the advice I was given in this list sometime around last Christmas (but can't find the thread now): you're bound to find some pesky application which is only available in 32bit and then you'll curse for having to reinstall. If anything, I'll install a VM to run it in. Have you tried setting -j1 and trying emerging it once more? I *ALWAYS* have -j1 in /etc/make.conf. Anyways, it turned out to be something completely different. Whilst doing additional Google searching, I stumbled across Foolproof Gentoo World Update Build Order at http://foxpa.ws/tag/package-keywords/ and it was proof against this fool, tooG. My problem was that the Gentoo install snapshot put in gcc-4.3.4, and emerge --update world pulled in gcc-4.4.3-r2. So far, so good. But after the first build, I forgot to gcc-config over to 4.4.3-r2 ... dohhh. Anyhow, after switching over, rebuilding gcc-4.4.3-r2, exiting, logging back in, unmerging gcc-4.3.4, and rebuilding glibc, I successfully emerged system and world. I'm now emerging xorg-x11. RANT Why on earth will xorg-x11 *NOT* build if I mask out various arabic, cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a kiosk machine at UN headquarters fer-cryin-out-loud. /RANT For future reference, after you switch gcc, you should run env-update and source /etc/profile. Then you don't have to log out and back in again. One could argue that one is easier than the other tho. ;-) Depends on the length of the password I guess. Dale :-) :-)
