I am trying to update, but i get that error.
#emerge -uavD system
!!! Please atach the folowing file when filling a report to bub.gentoo.org
!!!ERROR: sys-devel/gcc-config-2.0.0_beta2 faild.
ebuild.sh, Line 1894: Called dyncompile
ebuild.sh, Line 941: Called src_compile
grc-config-2.0.0_beta2.ebuild, Line 23: Called econf
!!!if you need suport post, the topmost build error, and the call stack if relevant1
This howto i folow, http://gentoo-wiki.com/TIP_Upgrade_Portage
*** This bug has been marked as a duplicate of 121327 ***
this is ther error that i get now,
/usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
Next time kindly read out gcc upgrading documentation before screwing up your system...
(In reply to comment #4)
> Next time kindly read out gcc upgrading documentation before screwing up your
WEl, usaly if i want to upgrade the hole system, i just emerge sync, etc-update, then emerge -n '>=sys-apps/portage-2.0.51' , after that linking
ln -s /usr/portage/profiles/<os>/<arch>/<profile-verision> make.profile
end findly emerge -uavD system . I did the same way on my second PC with out any arrors or warnings.
But i did not knew that had to upgrade GCC first before upgrading the hole system.
Thanks for the howto, i wil folwo that.
I folowd that howto http://www.gentoo.org/doc/en/gcc-upgrading.xml, i have also uprgaded GCC to 3.4.4-r1 . But it i get now the same error with other package. My system works fine, is not screwd up like you sayt on your last replay.
>>> Unpacking util-linux-2.13-pre6.tar.bz2 to /var/tmp/portage/util-linux-2.13_pre6/work
>>> Unpacking loop-AES-v3.1c.tar.bz2 to /var/tmp/portage/util-linux-2.13_pre6/work
!!! ERROR: sys-apps/util-linux-2.13_pre6 failed.
ebuild.sh, line 1894: Called dyn_unpack
ebuild.sh, line 694: Called src_unpack
!!! Sorry, no loop-AES support in this version
!!! If you need support, post the topmost build error, and the call stack if relevant.
Its unpacking, but when it wants to compile it stops and gives that error.
(In reply to comment #6)
That's no bug, and stop using hardmasked packages if you don't have any clue what are you doing.
(In reply to comment #8)
Ok, thats al what i a want it to know, couse i thought it was a bug.