[SOLVED] Upgraded GCC on Gentoo, different GCC version used when not root.

fakie_flip · 07-13-2012, 04:44 AM

On my Gentoo system, I had upgraded the gcc to match the version of gcc on another computer that would be a helper computer with distcc. I followed the Official Gentoo Docs on upgrading GCC. I recompiled libtool. Why am I using a different gcc version when I am my user than when I'm root? Even if run gcc-config -l as my user and not the root user, it shows the newer gcc selected, but that is not really the one being used.

Code:

bullshark@beastlinux ~ % gcc-config -l
 [1] i686-pc-linux-gnu-4.5.3
 [2] i686-pc-linux-gnu-4.5.3-hardenednopie
 [3] i686-pc-linux-gnu-4.5.3-hardenednopiessp
 [4] i686-pc-linux-gnu-4.5.3-hardenednossp
 [5] i686-pc-linux-gnu-4.5.3-vanilla
 [6] i686-pc-linux-gnu-4.6.2 *
 [7] i686-pc-linux-gnu-4.6.2-hardenednopie
 [8] i686-pc-linux-gnu-4.6.2-hardenednopiessp
 [9] i686-pc-linux-gnu-4.6.2-hardenednossp
 [10] i686-pc-linux-gnu-4.6.2-vanilla
bullshark@beastlinux ~ % gcc -v
Using built-in specs.
COLLECT_GCC=/usr/i686-pc-linux-gnu/gcc-bin/4.5.3/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.5.3 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.5.3/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.5.3/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --disable-fixed-point --without-ppl --without-cloog --disable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp --enable-esp --enable-libgomp --with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.5.3/python --enable-checking=release --disable-libgcj --with-arch=i686 --enable-languages=c,c++ --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo Hardened 4.5.3-r2 p1.5, pie-0.4.7'
Thread model: posix
gcc version 4.5.3 (Gentoo Hardened 4.5.3-r2 p1.5, pie-0.4.7)
bullshark@beastlinux ~ % su -
Password: 
beastlinux ~ # gcc -v
Using built-in specs.
COLLECT_GCC=/usr/i686-pc-linux-gnu/gcc-bin/4.6.2/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.6.2/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.6.2/work/gcc-4.6.2/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.6.2 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.2/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.6.2/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --disable-fixed-point --without-ppl --without-cloog --enable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp --enable-esp --enable-libgomp --with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.6.2/python --enable-checking=release --disable-libgcj --disable-libquadmath --with-arch=i686 --enable-languages=c,c++ --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo Hardened 4.6.2 p1.4, pie-0.5.0'
Thread model: posix
gcc version 4.6.2 (Gentoo Hardened 4.6.2 p1.4, pie-0.5.0) 
beastlinux ~ #

segmentation_fault · 07-13-2012, 09:23 AM

Well, I have the same configuration on my distcc system, and except very few packages, everything compiles and runs fine, despite the gcc version mismatch.

fakie_flip · 07-14-2012, 11:11 AM

I ran an emerge --depclean, and it removed the older gcc version and left just the new one. So now when I type gcc -v as non root, it shows the same new version that is shown when I typed gcc -v as root.

BTW, It's highly discouraged to use gcc versions that aren't the same with distcc. Everywhere I've read about distcc, it has said that. However, I have also read that it is ok to be off by one point release eg. if your versions are both 4.5.x eg. one is 4.5.6 and the other is 4.5.8. I suggest you look at the system with the older gcc version, and then upgrade it to be the same as the system with the newer version. For me, I did added this, and then upgraded my gcc. Be sure to read the Gentoo's Upgrading GCC guide. You will need to rebuild libtool and depending on your gcc version, you may need to do a few additional steps. I've had absolutely no problems with any of this.

bullshark@beastlinux ~ % cat /etc/portage/package.accept_keywords
=sys-devel/gcc-4.6.2 ~x86