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/gtkmm/gtkmm-2.2.10.ebuild: libtoolize -c -f --automake ./dev-cpp/gtkmm/gtkmm-2.2.11.ebuild: libtoolize -c -f --automake ./dev-cpp/gtkmm/gtkmm-2.2.8.ebuild: [ "${ARCH}" = "amd64" ] && libtoolize -c -f 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
I'm on it.
I cleaned out 2.2.10 and 2.2.11 during routine redundant version removing across gnome team managed packages. 2.2.8 remains in with libtoolize usage after my cleanup, as it's the last ia64 stable version in SLOT="2". Newer versions that ia64 has stable are from SLOT="2.4"
(In reply to comment #2) > 2.2.8 remains in with libtoolize usage after my cleanup, as it's the last ia64 > stable version in SLOT="2". Newer versions that ia64 has stable are from > SLOT="2.4" Not any more, please remove 2.2.8 and close this bug... Keywords for dev-cpp/gtkmm: | a a a h i m m p p p s s s s x x | l m r p a 6 i p p p 3 h p p 8 8 | p d m p 6 8 p c c c 9 a a 6 6 | h 6 a 4 k s 6 - 0 r r - | a 4 4 m c c f | a - b | c f s | o b d | s s | d ----------+-------------------------------- 2.2.8 | + + + + + + + 2.2.11 | + + ~ ~ + + + 2.2.12 | + + + + + + + + + +
pruned
