Bugzilla Bug 13083

During "emerge -u system" (after bootstrap/stage2) db fails to compile stoping
"emerge -u system". It appears that the installation of gcc-3.2.1-r6 (an ALPHA
ebuild) the gcc binaries from /usr/bin. 'cc' is symlinked to 'gcc' within
/usr/bin

Sorry ?  I do not understand what you are trying to say ?  Please include
logs, etc.  Normally /usr/bin/cc is a symlink to gcc.  with gcc-3.2.1-r6 however,
it is a shell script, so if it is not, it usually means you have an old
sys-devel/gcc-config.  So update that (current version should be 1.2.7), and
see if it fixes.  If not, you should really include more info.

(btw, if you have ~x86, you should not moan about ALPHA ?)

Well then it seems that gcc-config was not being installed via the "emerge -u
system" before db was compiled. Was it not a dependancy? If gcc-config is needed
for a proper compiler environment then it certainly should be!

Infact its not now:

deperdo gcc # emerge search gcc
Searching...   
[ Results for search key : gcc ]
[ Applications found : 5 ]
 
[...]

*  sys-devel/gcc
      Latest version available: 3.2.1-r6
      Latest version installed: 3.2.1-r6
      Size of downloaded files: 21,271 kB
      Homepage:    http://www.gnu.org/software/gcc/gcc.html
      Description: Modern C/C++ compiler written by the GNU people

[...]

gcc-3.2.1-r6 is installed. Let's remove gcc-config...:

deperdo gcc # emerge -C sys-devel/gcc-config

 sys-devel/gcc-config
    selected: 1.2.7
   protected: none
     omitted: none

>>> Packages in red are slated for removal.
>>> Packages in green will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1 
>>> Unmerging sys-devel/gcc-config-1.2.7...
No package files given... Grabbing a set.
<<<        obj /usr/sbin/gcc-config
--- !empty dir /usr/sbin
--- !empty dir /usr
>>> Regenerating /etc/ld.so.cache...

 * GNU info directory index is up-to-date.

So, now according to you, I have a broken compiler environment. Let's update my
system...:

deperdo gcc # emerge -up system

These are the packages that I would merge, in order:

Calculating system dependencies ...done!
[ebuild    U ] sys-libs/glibc-2.3.1-r3 [2.3.1-r2]
[ebuild  N   ] sys-devel/libperl-5.8.0 
[ebuild    U ] sys-devel/perl-5.8.0-r8 [5.8.0-r7]
[ebuild  N   ] dev-perl/ExtUtils-MakeMaker-6.05-r4 
[ebuild  N   ] dev-perl/Safe-2.09 
[ebuild    U ] net-misc/dhcpcd-1.3.22_p4 [1.3.22_p3-r2]

A couple of things need to get updated, but no gcc-config! If gcc-3.2.1-r6 does
not have /usr/bin/cc, and gcc-config-1.2.7 does have /usr/bin/cc, and
/usr/bin/cc is required to build db therefore shouldnt gcc-config be required to
be installed along with gcc-3.2.1-r6? Especially when you're installing a fresh
system?

And regarding the ALPHA comment...
# Distributed under the terms of the GNU General Public License v2
# $Header: /home/cvsroot/gentoo-x86/sys-devel/gcc/gcc-3.2.1-r6.ebuild,v 1.4
2002/12/23 17:49:58 azarah Exp $

[...snip...]

pkg_setup() {
        echo
        eerror "This is a very alpha ebuild and changes in here"
        eerror "are not yet set in stone!  Please do NOT merge"
        eerror "this if you are not a developer!"
#       die
}

You said so yourself. gcc-3.2.1-r6 is an ALPHA ebuild.

OK.

------------------------------

nosferatu pam_unix # USE="build bootstrap" emerge -ep gcc

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N   ] sys-apps/portage-2.0.46-r4 
*** Please update portage to the above version before proceeding.
    Failure to do so may result in failed or improper merges.
    A simple 'emerge -u portage' is sufficient.

[ebuild  N   ] sys-kernel/linux-headers-2.4.19 
[ebuild  N   ] sys-apps/baselayout-1.8.5.8 
[ebuild  N   ] sys-devel/binutils-2.13.90.0.16-r1 
[ebuild  N   ] sys-libs/glibc-2.3.1-r5 
[ebuild  N   ] sys-apps/texinfo-4.3-r1 
[ebuild  N   ] sys-devel/gcc-config-1.2.7 
[ebuild  N   ] sys-libs/zlib-1.1.4 
[ebuild  N   ] sys-devel/gcc-3.2.1-r6 

nosferatu pam_unix # 

maybe you had only exec the following

emerge -pu world --deep

closing #13451 as dup of this

*** Bug 13451 has been marked as a duplicate of this bug. ***