Created attachment 475710 [details] emerge --info '=gnome-extra/gnome-system-monitor-3.22.2::gentoo' I have just synced my portage tree and I'm trying to move from gnome 3.18 to gnome 3.22. Everything went fine except gnome-system-monitor 3.22.2 Here are few details: uname -a Linux 4.9.16-gentoo #1 SMP Thu Jun 8 15:19:02 CEST 2017 x86_64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz GenuineIntel GNU/Linux * ERROR: gnome-extra/gnome-system-monitor-3.22.2::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=gnome-extra/gnome-system-monitor-3.22.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=gnome-extra/gnome-system-monitor-3.22.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/gnome-extra/gnome-system-monitor-3.22.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/gnome-extra/gnome-system-monitor-3.22.2/temp/environment'. * Working directory: '/var/tmp/portage/gnome-extra/gnome-system-monitor-3.22.2/work/gnome-system-monitor-3.22.2' * S: '/var/tmp/portage/gnome-extra/gnome-system-monitor-3.22.2/work/gnome-system-monitor-3.22.2' >>> Failed to emerge gnome-extra/gnome-system-monitor-3.22.2, Log file: emerge -pqv '=gnome-extra/gnome-system-monitor-3.22.2::gentoo' [ebuild N ] gnome-extra/gnome-system-monitor-3.22.2 USE="X systemd" I have re-emerged the whole system and gnome but problem is still there, do you know where is the problem ? Thanks in advance for your reply Ben
Created attachment 475712 [details] build.log
# gcc -v Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/5.4.0/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/5.4.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/5.4.0 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/5.4.0 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/5.4.0/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/5.4.0/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/5.4.0/python --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 5.4.0-r3 p1.3, pie-0.6.5' --enable-libstdcxx-time --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64 --disable-altivec --disable-fixed-point --enable-targets=all --disable-libgcj --enable-libgomp --disable-libmudflap --disable-libssp --disable-libcilkrts --disable-libmpx --enable-vtable-verify --enable-libvtv --enable-lto --without-isl --enable-libsanitizer Thread model: posix gcc version 5.4.0 (Gentoo 5.4.0-r3 p1.3, pie-0.6.5)
This looks like GCC upgrade fallout, please check out: https://gentoo.org/support/news-items/2015-10-22-gcc-5-new-c++11-abi.html
Yes it was. It solved it. I did a massive upgrade from a ~200 days ago portage, so a lot of things were different. Now I have solved after some rebuilts. gcc, glibc, glib and everything I have found as a dependency from gnome-system-monitor .ebuild file. Now it seems to work fine. Thanks a lot
