After running the bootstrap from a 1.4_rc4 stage1 tarball with the CHOST set to i686-pc-linux-gnu in /etc/make.conf (the default value), the gcc toolchain moves from /usr/i586-pc-linux-gnu/gcc-bin/3.2 to /usr/i686-pc-linux-gnu/gcc-bin/3.2. Unless the PATH is updated accordingly, the gcc-config wrapper program will not be able to locate the gcc binary and so will call the /usr/bin/gcc-config script on every invocation of gcc which slows down the rest of the build a lot (I would estimate 2-3x slower on my machine). After getting tired of waiting on that, accidentally messing up my fledgling system, and then starting over, I ran "env-update" (which may or may not be necessary, I don't know) and "source /etc/profile" after the stage1 bootstrap finished. My PATH was properly updated, and now gcc executes without running the gcc-config script and python, and the build of the rest of my system is progressing much faster. Note: It looks like the install doc once had a second "source /etc/profile" instruction that was removed in response to bug 16119. Reproducible: Always Steps to Reproduce:
I've done just the same thing (bootstrapping from stage1 tarball), having CHOST on i686... but after the bootstrapping gcc-config listed the correct profile (i686) and had it in the path (environment). In the bootscript.sh, there are some references to gcc-config selecting the correct invironment, so I guess it should normally be fine. I'm invalidating this bug, however, if you are absolutely certain (because you retried it again, or have other ppl with the same troubles), please reopen the bug.
