The following ebuilds are found to have broken autotools handling, as they run libtoolize directly (they never should, instead they should call eautoreconf in autotools.eclass, read http://www.gentoo.org/proj/en/qa/autofailure.xml for more information): ./dev-cpp/gnome-vfsmm/gnome-vfsmm-2.10.0.ebuild: libtoolize --copy --force ./dev-cpp/gnome-vfsmm/gnome-vfsmm-2.11.1.ebuild: libtoolize --copy --force ./dev-cpp/gnome-vfsmm/gnome-vfsmm-2.6.1.ebuild: libtoolize --copy --force Please cleanup the ebuilds by asking for stable marking, removing obsolete ebuilds with no relevant keywords, or porting the fixes in newer versions (if presents) to properly handle autotools. Thanks, Diego
Created attachment 105921 [details] gnome-vfsmm-2.12.0/config.log I guess this is the same error: # emerge --oneshot =dev-cpp/gnome-vfsmm-2.12.0 [...cut...] /bin/sh ../../libtool --tag=CXX --mode=compile i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -DG_LOG_DOMAIN=\"libgnomevfsmm\" -I../../libgnomevfs -I../../libgnomevfs -pthread -DORBIT2=1 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/gnome-vfs-module-2.0 -O2 -mtune=i686 -pipe -MT transfer.lo -MD -MP -MF .deps/transfer.Tpo -c -o transfer.lo transfer.cc i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -DG_LOG_DOMAIN=\"libgnomevfsmm\" -I../../libgnomevfs -I../../libgnomevfs -pthread -DORBIT2=1 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/gnome-vfs-module-2.0 -O2 -mtune=i686 -pipe -MT mime-handlers.lo -MD -MP -MF .deps/mime-handlers.Tpo -c mime-handlers.cc -fPIC -DPIC -o .libs/mime-handlers.o i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -DG_LOG_DOMAIN=\"libgnomevfsmm\" -I../../libgnomevfs -I../../libgnomevfs -pthread -DORBIT2=1 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/gnome-vfs-module-2.0 -O2 -mtune=i686 -pipe -MT transfer.lo -MD -MP -MF .deps/transfer.Tpo -c transfer.cc -fPIC -DPIC -o .libs/transfer.o ../../libgnomevfs/libgnomevfsmm/mime-handlers.h:75: error: expected constructor, destructor, or type conversion before '*' token make[4]: *** [mime-handlers.lo] Error 1 make[4]: *** Waiting for unfinished jobs.... mv -f .deps/transfer.Tpo .deps/transfer.Plo make[4]: Leaving directory `/compile/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs/libgnomevfsmm' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/compile/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs/libgnomevfsmm' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/compile/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs' make[1]: *** [all] Error 2 make[1]: Leaving directory `/compile/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs' make: *** [all-recursive] Error 1 !!! ERROR: dev-cpp/gnome-vfsmm-2.12.0 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1255: Called gnome2_src_compile gnome2.eclass, line 71: Called die !!! compile failure !!! If you need support, post the topmost build error, and the call stack if relevant.
same here, why do they commit non-woking updates? emerge -e world is no fun atm: ../../libgnomevfs/libgnomevfsmm/mime-handlers.h:75: error: expected constructor, destructor, or type conversion before '*' token distcc[28378] ERROR: compile mime-handlers.cc on localhost failed make[4]: *** [mime-handlers.lo] Error 1 make[4]: *** Waiting for unfinished jobs.... mv -f .deps/transfer.Tpo .deps/transfer.Plo mv -f .deps/async.Tpo .deps/async.Plo make[4]: Leaving directory `/space/tmp/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs/libgnomevfsmm' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/space/tmp/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs/libgnomevfsmm' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/space/tmp/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs' make[1]: *** [all] Error 2 make[1]: Leaving directory `/space/tmp/portage/gnome-vfsmm-2.12.0/work/gnome-vfsmm-2.12.0/libgnomevfs' make: *** [all-recursive] Error 1 !!! ERROR: dev-cpp/gnome-vfsmm-2.12.0 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1255: Called gnome2_src_compile gnome2.eclass, line 71: Called die !!! compile failure !!! If you need support, post the topmost build error, and the call stack if relevant.
I also get this error; however it appears to be unrelated to this bug (the 2.12.0 ebuild correctly calls eautoreconf rather than directly using libtoolize)
(In fact, I think that error is the same one reported in bug 147331...)
I have that problem too
2.16.0 is now stable on all architectures. please reopen if you still have any issues.
