GCC 4.1.2->4.2.0 problem (glibc-2.6 fails) [Solved]

[Mring]

First post of mine here, just got Sabayon on here this morning. I'm new to Linux, but giving it all a good try.

Anyway, I was planning on doing a world update & all that fun stuff, so decided to update GCC first.

I did a sync for emerge & layman, then did

Code: Select all

emerge -uav gcc

.. Just as it says in the wiki. It did its thing, I did mine, came back later to find this:

Code: Select all

>>> Emerging (5 of 5) sys-libs/glibc-2.6 to /
 * glibc-2.6-patches-1.6.tar.bz2 RMD160 ;-) ...                           [ ok ]
 * glibc-2.6-patches-1.6.tar.bz2 SHA1 ;-) ...                             [ ok ]
 * glibc-2.6-patches-1.6.tar.bz2 SHA256 ;-) ...                           [ ok ]
 * glibc-2.6-patches-1.6.tar.bz2 size ;-) ...                             [ ok ]
 * glibc-2.6.tar.bz2 RMD160 ;-) ...                                       [ ok ]
 * glibc-2.6.tar.bz2 SHA1 ;-) ...                                         [ ok ]
 * glibc-2.6.tar.bz2 SHA256 ;-) ...                                       [ ok ]
 * glibc-2.6.tar.bz2 size ;-) ...                                         [ ok ]
 * glibc-ports-2.6.tar.bz2 RMD160 ;-) ...                                 [ ok ]
 * glibc-ports-2.6.tar.bz2 SHA1 ;-) ...                                   [ ok ]
 * glibc-ports-2.6.tar.bz2 SHA256 ;-) ...                                 [ ok ]
 * glibc-ports-2.6.tar.bz2 size ;-) ...                                   [ ok ]
 * glibc-libidn-2.6.tar.bz2 RMD160 ;-) ...                                [ ok ]
 * glibc-libidn-2.6.tar.bz2 SHA1 ;-) ...                                  [ ok ]
 * glibc-libidn-2.6.tar.bz2 SHA256 ;-) ...                                [ ok ]
 * glibc-libidn-2.6.tar.bz2 size ;-) ...                                  [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking glibc-2.6.tar.bz2 ;-) ...                                     [ ok ]
 * checking glibc-libidn-2.6.tar.bz2 ;-) ...                              [ ok ]
 * checking glibc-ports-2.6.tar.bz2 ;-) ...                               [ ok ]
 * checking glibc-2.6-patches-1.6.tar.bz2 ;-) ...                         [ ok ]
 * You still haven't deleted //etc/locales.build.
 * Do so now after making sure //etc/locale.gen is kosher.

!!! ERROR: sys-libs/glibc-2.6 failed.
Call stack:
  ebuild.sh, line 1637:   Called dyn_setup
  ebuild.sh, line 704:   Called qa_call 'pkg_setup'
  ebuild.sh, line 44:   Called pkg_setup
  glibc-2.6.ebuild, line 1094:   Called die

!!! lazy upgrader detected
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.6/temp/build.log'.


I thought perhaps second time would be a charm, so I tried 'emerge glibc' and got an identical result. "Lazy upgrader detected" -- I think it caught me.

I ran gcc-config -l I think it is, and 4.1.2 is still default, and I reckon I should leave it that way until glibc-2.6 is installed and happy.

I googled it, found two links, one useless the other a dead link. Do I just need to delete //etc/locales.build, like it complains about?

Thanks for any help, guys.

[wolfden]

yea I simply did mv /etc/locales.build /etc/locales.build.bak
and all was good

[Mring]

That got her going, thanks for the help!

[DarkMind]

and put the locales that you need in /etc/locale.gen (for my case, es_ES.UTF-8 UTF-8) or glibc compile all the locales and take more time and disk wasted