Stage 1/3 Installation Support - 2005.0/2005.1 & GCC 3.4.4

Bob P · Last edited by Bob P on Sat Feb 18, 2006 3:13 pm; edited 8 times in total

Stage 1/3 Installation -- 2005.0/2005.1 & GCC 3.4.4 -- Official Support Thread

This is the Offical Support Thread for the Stage 1/3 Installation Method for Gentoo 2005.0 & GCC 3.4.4. Please post all of your support requests to this thread. :idea:

NOTE: The Stage 1/3 Guide is an ADVANCED installation method. Support is offered for questions that uniquely pertain to the Stage 1/3 installation method. Support is NOT offered for Gentoo Fundamentals questions. New Users with general questions about Gentoo are advised to RTM or to seek help in the other threads in the Gentoo Forums. :!:

How To Ask For Support

When asking for support, please give us all of the information that we need to approach your problem. This would include:

1. the full output of the error message you received
2. the output of "emerge --info"
3. the name of the tarball that you installed from

Please Note

To efficiently utilize the time that I spend providing support, I will only respond to support requests that are posted to this thread, so that the answers will remain available as reference material for anyone who may need to refer to them. I will no longer repond to ANY Personal Messages or e-mails requesting support. All Personal Messages sent to me that contain personalized support requests will be deleted without a reply.

Please post ALL support requests in the Stage 1/3 Support Thread, where everyone can benefit from the answer!

Thanks, and have fun! :wink:

How To Update After a Stage 1/3 Install

:arrow:

Download the Toolkit Update Scripts by hielvc and minderaser http://forums.gentoo.org/viewtopic-t-314985-start-481.html

Quick Reference: Common Errors Associated with Stage 1/3 Installs

:arrow:

Emerge --sync: A New Version of Portage is Available http://forums.gentoo.org/viewtopic-t-345545-start-155.html

:arrow:

Security Violation: A file exists that is not in the manifest http://forums.gentoo.org/viewtopic-t-325007.html

:arrow:

Framebuffer Problems with 2.6.12 Kernels http://forums.gentoo.org/viewtopic-t-345229-start-40.html

:arrow:

Problems Setting Hostname & Domainname http://forums.gentoo.org/viewtopic-t-345545-start-35.html

:arrow:

"emerge -e system" fails at python-fchksum http://forums.gentoo.org/viewtopic-t-314985-start-401.html

:arrow:

C Compiler Cannot Create Executables: http://forums.gentoo.org/viewtopic-t-294109.html

:arrow:

Glibc Will Not Compile: http://forums.gentoo.org/viewtopic-t-314985-start-42.html

:arrow:

Failure on First Boot: http://forums.gentoo.org/viewtopic-t-299646-start-31.html

:arrow:

Gensplash and Bootsplash Problems: http://forums.gentoo.org/viewtopic-t-299646-start-19.html

:arrow:

Genkernel - Unsupported: http://forums.gentoo.org/viewtopic-t-299646-start-176.html

:arrow:

Reiser 4 - Unsupported: http://forums.gentoo.org/viewtopic-t-299646-start-51.html

:arrow:

AMD64 - Unsupported: http://forums.gentoo.org/viewtopic-t-314985-start-427.html

Off-Topic: Common Problems NOT Related to the Stage 1/3 Installation Method

:arrow:

Gentoo Fundamentals. Basic questions about Gentoo are not appropriate for this thread. New Users with questions are advised to RTM and are invited to read Installing Gentoo and Portage & Programming.

:arrow:

Grub Errors. Grub errors are not germane to the Stage 1/3 Guide. If you need help in learning how to install the boot loader, read the sticky Grub Error Collection thread. Every possible Grub configuration problem has already been addressed in that thread.

:arrow:

Emerge Command Syntax. If you've never installed Gentoo before, or if you just don't know the syntax of the "emerge" command, then you need to review the Gentoo Fundamentals and the man page for the emerge command. If you still have problems after doing that, I would seek help in the Support Forums such as Installing Gentoo and Portage & Programming.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

Bob P · Posted: Sun Jun 05, 2005 5:42 pm Post subject:

-outdated information removed-
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

Gentoonie · Posted: Mon Jun 06, 2005 2:25 pm Post subject:

For people that are running a jackass system and want to upgrade their gcc 3.4.3 to gcc 3.4.4 and _dont_ want to run into the dreaded libstdc++.so.6 problem, heres a simple solution:

For some reason, on emerging gcc.3.4.4, portage removes the complete tree of gcc 3.4.3 during runtime to update it with 3.4.4, so theres no libstdc++.so.6 left. Unfortunately this one is needed for further emerges and even gcc-config requires this file. Do a

Clyde · Posted: Mon Jun 06, 2005 3:38 pm Post subject:

Ignorant of the multislot option, I accomplished what I hope is the same result--I guess (?). I temporarily set AUTOCLEAN=no in make.conf just long enough to emerge gcc 3.4.4 and set it as default with gcc-config before a subsequent toolchain rebuild (using hielvc's emwrap) removed it. No errors since....

I also modified the package.keywords gcc line to "~sys-devel/gcc-3.4.4 ~x86", but now I'm considering changing that ~ to an =, and similarly locking down other toolchain components, to prevent any accidental updates....

Bob P · Posted: Mon Jun 06, 2005 5:37 pm Post subject:

Bob P · Posted: Mon Jun 06, 2005 5:39 pm Post subject:

yep -- i did post it -- in the Jackass! Support Group.

http://forums.gentoo.org/viewtopic-t-334279-start-199.html

for a minute there, i thought that my memory was failing! :oops:

_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

Gentoonie · Posted: Mon Jun 06, 2005 5:47 pm Post subject:

Bob P · Posted: Mon Jun 06, 2005 6:07 pm Post subject:

yeah, i know what you mean. sometimes i feel like i'm tracking too many threads.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

starrbuck · Posted: Tue Jun 07, 2005 3:49 pm Post subject:

Hi Bob,

I'm using Jackass 2005.0 from the Athlon XP tar file. My system upgraded itself to GCC 3.4.4 and did NOT encounter the missing libstdc++.so.6 issue. Wonder why it worked with no interference on my part?

Do I need to rebuild the toolkit or do anything else now that 3.4.4 is installed?

Bob P · Posted: Tue Jun 07, 2005 4:08 pm Post subject:

Bob P · Posted: Tue Jun 07, 2005 5:29 pm Post subject:

starrbuck · Posted: Tue Jun 07, 2005 7:17 pm Post subject:

Bob P · Posted: Tue Jun 07, 2005 8:40 pm Post subject:

the problem that alot of people fail to realize is that the possibility for human error is introduced with every revision and/or upgrade. :idea:

i hate to say it, but i have to come to expect that the minor bugfix revisions/upgrades to the toolkit typically do more harm than good -- during the first few days of their life cycle they completely b0rk everyone's system, just like GCC 3.4.4 has done this week. it takes a good week of troubleshooting to weed-out the truly stupid mistakes that very smart people often make. then, once the simple oversights are fixed, the bugfixes actually do what they're supposed to do.

anyone that's gullible enough to put a testing branch update into their cron job is just asking to have their box turned into a bug magnet. :roll:

IMO, the best thing to do is not to fall sucker for a version upgrade as soon as it comes out. let some other guy who's obsessed about having the most-up-to-date system on his block be the guy who's updating every day and reporting all of the bugs. :wink:

and don't upgrade unless the bugfixes in the update actually solve a problem that you've encountered. in other words -- if it ain't broke, don't fix it. :!:

_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks

starrbuck · Posted: Tue Jun 07, 2005 9:16 pm Post subject:

I agree!

What would have been the best way to make it not have upgraded to GCC 3.4.4? Put something specific in the /etc/portage/package.keywords file to make it stay at 3.4.3?
_________________
Gentoo Linux is groovy, baby! Yeah!

nightmorph · Developer Joined: 23 Jan 2005 Posts: 1382 Location: SoCal

You need to modify the atom in front of the necessary packages in package.keywords; use an = in front of the appropriate toolchain packages to lock them down. Then you will not be upgraded to gcc 3.4.4. So you'd end up with =whatever-category/gcc-3.4.3-r3 ~x86 in package.keywords. It would be a good idea to apply the same atom to binutils and the other toolchain packages, as they all support one another. I'm not sure that upgrading the other toolkit components while not upgrading gcc is the best idea.
_________________
<UzzaDead> What is CONFIG_USB_MON?
<petteyg> A Jamaican USB configuration?

dirtyepic: "We have more cupholders."

GDP || PR

cynric · Posted: Tue Jun 07, 2005 10:51 pm Post subject:

First off, nice howto, Bob P. In regards to the last two posts, would it also be aesthetically appropriate to put ">whatever-category/gcc-3.4.3" in package.mask?
_________________
"This Snow Crash thing -- is it a virus, a drug, or a religion?" "What's the difference?"
-- Neal Stephenson - Snow Crash

jmbsvicetto · Posted: Wed Jun 08, 2005 12:35 am Post subject:

cynric · Posted: Wed Jun 08, 2005 1:05 am Post subject:

Er, yes. A simple, but grosse error on my part.
_________________
"This Snow Crash thing -- is it a virus, a drug, or a religion?" "What's the difference?"
-- Neal Stephenson - Snow Crash

Bob P · Posted: Wed Jun 08, 2005 7:06 am Post subject:

Bob P · Posted: Wed Jun 08, 2005 7:07 am Post subject:

starrbuck · Posted: Wed Jun 08, 2005 5:14 pm Post subject:

starrbuck · Posted: Fri Jun 10, 2005 12:29 am Post subject:

Never mind. I put this in my package.keywords:

nightmorph · Developer Joined: 23 Jan 2005 Posts: 1382 Location: SoCal

Good show. That's the better way to do it. My suggestion was only for users who absolutely did not want an upgrade of gcc past what they had, even ignoring -r# revisions. I, too, have no reason to upgrade to 3.4.4; there seem to be too many problems with it; so much for it being a supposed "bug fix" release!

I might consider it worth upgrading once more reports trickle in about if it affects the efficient running of a system once all world packages are recompiled with it. If there are significant performance gains to be had, then maybe I'll update. For now, it's a bit too bleeding edge, especially if my computer ends up doing the bleeding!

But kudos to your particular package.keywords; that allows for more controlled upgrading without moving up to 3.4.4.
_________________
<UzzaDead> What is CONFIG_USB_MON?
<petteyg> A Jamaican USB configuration?

dirtyepic: "We have more cupholders."

GDP || PR

Bob P · Posted: Fri Jun 10, 2005 5:21 pm Post subject:

Bob P · Posted: Fri Jun 10, 2005 5:23 pm Post subject:

just to make the previous comments clear: this is what you need to do to put GCC 3.4.3 back: