Difference between revisions of "Toolchain update"
Revision as of 20:29, 3 October 2013
This guide explains how to upgrade the Funtoo toolchain to the new version available. With this toolchain update comes some other core packages bumps that were depending on the new toolchain.
|Note:||This toolchain update affects the users of the current tree. Stable users should not update to this toolchain yet as many stable packages may not build with it.|
Funtoo currently provides the following core package versions:
Those core packages will be updated to the following versions:
Unmasking the packages
To unmask the packages, run emerge --sync. If you are using the funtoo-current, they should now be unmasked. To perform this manually (no longer necessary,) do this:
# install -d /etc/portage/package.unmask # echo ">=sys-devel/gcc-4.8.1" >> /etc/portage/package.unmask/toolchain # echo "=sys-devel/binutils-2.23.1" >> /etc/portage/package.unmask/toolchain # echo "=sys-kernel/linux-headers-3.7" >> /etc/portage/package.unmask/toolchain # echo "=sys-libs/glibc-2.18" >> /etc/portage/package.unmask/toolchain # echo "=sys-fs/udev-171-r9" >> /etc/portage/package.unmask/toolchain
Easier way is to copy
funtoo-toolchain from /usr/portage/profiles/package.mask, assuming that /etc/portage/package.unmask is a directory:
# cp /usr/portage/profiles/package.mask/funtoo-toolchain /etc/portage/package.unmask
Keywords changes for stable users
If Stable users are not afraid to upgrade their toolchain, they must add the correct keywords too:
# install -d /etc/portage/package.keywords # echo ">=sys-devel/gcc-4.8.1 **" >> /etc/portage/package.keywords/toolchain # echo "=sys-devel/binutils-2.23.1 **" >> /etc/portage/package.keywords/toolchain # echo "=sys-kernel/linux-headers-3.7 **" >> /etc/portage/package.keywords/toolchain # echo "=sys-libs/glibc-2.18 **" >> /etc/portage/package.keywords/toolchain # echo "=sys-fs/udev-171-r9 **" >> /etc/portage/package.keywords/toolchain
Upgrading to the new toolchain
As the dependencies have been adjusted so the packages are built in the right order, no user manipulation is required. Updating everything should work out of the box, but to ensure that no unwanted package is updated between the toolchain parts, proceed as following:
# emerge --sync # emerge -1 glibc # emerge -uNDav @world
What about libtool?
libtool is automatically rebuilt during the update process. This avoids any manual steps to be executed after the update.
Rebuilding the whole system?
Some people argue that this is necessary to rebuild the whole system (even twice) after a toolchain upgrade. This is never necessary, but users who changed their CFLAGS or CXXFLAGS due to a new available arch or optimization flag are welcome to do so, if they want. However, remember that this is never necessary.
Case of depclean
After switching to new gcc, it can be cleaned (accidentally) by emerge ---depclean, it is recommended to save older gcc for failover
# emerge -av --depclean --exclude sys-devel/gcc
After the update, if any package fails to start with a shared library missing problem, try to run: