|Summary:||dev-cpp/gtkglextmm-1.0.1: aclocal/autoconf/automake called directly|
|Product:||Gentoo Linux||Reporter:||Diego Elio Pettenò (RETIRED) <flameeyes>|
|Component:||New packages||Assignee:||GNOME C++ Bindings Maintainers (OBSOLETE) <gnome-mm+disabled>|
|Package list:||Runtime testing required:||---|
|Bug Depends on:|
|Bug Blocks:||226305, 228471|
Description Diego Elio Pettenò (RETIRED) 2008-06-14 11:44:06 UTC
Please never call autotools directly, instead use eautoreconf (or eautomake, and JUST THESE TWO) from autotools.eclass. If you have any reason why those don't work, please let me know to fix them. Thanks, Diego
Comment 1 Rémi Cardona 2008-06-14 15:23:55 UTC
Right, I know we should not be calling those (and no one really knows why it's _really_ needed, just that it has failed in the past on amd64) But then again, I would like to tree clean this precise ebuild, which should solve the issue :)
Comment 2 Gilles Dartiguelongue 2008-06-29 14:20:36 UTC
16:16 < EvaSDK_> !rdep gtkglextmm 16:16 < jeeves> dev-cpp/gtkglextmm <- dev-python/visual 16:16 < EvaSDK_> rdep visual 16:16 < EvaSDK_> !rdep visual 16:16 < jeeves> dev-python/visual <- net-analyzer/scapy:visual better start by stabilizing 1.2.0-r1 (and please fix the sed on Makefile.in to .am + eautomake, it's probably the root of borkage that cause these lines to be added :)).
Comment 3 Rémi Cardona 2008-06-29 22:19:35 UTC
(In reply to comment #2) > better start by stabilizing 1.2.0-r1 Agreed > (and please fix the sed on Makefile.in to > .am + eautomake, it's probably the root of borkage that cause these lines to be > added :)). Nope, the sed line is fine. Nothing gets built in there except for documentation. Rerunning eautomake for that is just a waste of time. However, I need to review all gnome-mm ebuilds for the examples/tests stuff, so I'll look at the documentation too.