libtool: link: (cd ".libs" && rm -f "libgiomm-2.4.so.1" && ln -s "libgiomm-2.4.so.1.3.0" "libgiomm-2.4.so.1") libtool: link: (cd ".libs" && rm -f "libgiomm-2.4.so" && ln -s "libgiomm-2.4.so.1.3.0" "libgiomm-2.4.so") libtool: link: ( cd ".libs" && rm -f "libgiomm-2.4.la" && ln -s "../libgiomm-2.4.la" "libgiomm-2.4.la" ) make[2]: Leaving directory `/var/tmp/portage/dev-cpp/glibmm-2.30.1/work/glibmm-2.30.1/gio/giomm' Making all in examples make[2]: Entering directory `/var/tmp/portage/dev-cpp/glibmm-2.30.1/work/glibmm-2.30.1/examples' /usr/bin/glib-compile-schemas --targetdir=settings ./settings make[2]: *** [settings/gschemas.compiled] Ungültiger Maschinenbefehl make[2]: Leaving directory `/var/tmp/portage/dev-cpp/glibmm-2.30.1/work/glibmm-2.30.1/examples' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/var/tmp/portage/dev-cpp/glibmm-2.30.1/work/glibmm-2.30.1' make: *** [all] Fehler 2 * ERROR: dev-cpp/glibmm-2.30.1 failed (compile phase): * emake failed * * If you need support, post the output of 'emerge --info =dev-cpp/glibmm-2.30.1', * the complete build log and the output of 'emerge -pqv =dev-cpp/glibmm-2.30.1'. * The complete build log is located at '/var/tmp/portage/dev-cpp/glibmm-2.30.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-cpp/glibmm-2.30.1/temp/environment'. * S: '/var/tmp/portage/dev-cpp/glibmm-2.30.1/work/glibmm-2.30.1'
Please set LC_MESSAGES=C and attach the entire build.log. Also post your emerge --info here.
Created attachment 302577 [details] The build log
Created attachment 302579 [details] Output of emerge --info
done...
It seems that there is some problem with /usr/bin/glib-compile-schemas Can you rebuild the package owning that file?
(In reply to comment #5) > It seems that there is some problem with /usr/bin/glib-compile-schemas > Can you rebuild the package owning that file? already done, still failing to compile, same output ...
The procesor is i7, march is core2 (-O0 is "odd" but whatever), so it's most likely a dupe of bug 396609.
*** This bug has been marked as a duplicate of bug 396609 ***