There are a few packages that calls elibtoolize before autoretooling. If
elibtoolize is called and then the configure is re-generated, the configure
patches that can be necessary (for example Gentoo/FreeBSD's patches) are being
Please remember that if you call libtoolize --copy --force you must also
re-call aclocal and autoconf.
If needed, you can use eautoreconf function in autotools eclass that takes
care of calling all the needed autotools to regenerate their support files.
app-admin/fam/fam-2.7.0-r4.ebuild: elibtoolize called before autoretooling
app-crypt/heimdal/heimdal-0.7.1.ebuild: elibtoolize called before
gnome-base/gnome-core/gnome-core-1.4.2-r1.ebuild: elibtoolize called before
media-gfx/gphoto2/gphoto2-2.1.6.ebuild: elibtoolize called before
autoretooling [gnome | email@example.com]
media-libs/faad2/faad2-2.0-r7.ebuild: elibtoolize called before autoretooling
Affected herds: gnome, kerberos
Affected devs: firstname.lastname@example.org, email@example.com
Heimdal is fixed now.
Also php (at least dev-lang/php-5.0) calls elibtoolize before libtoolize.
Maybe you can just use eautoreconf followed by elibtoolize, it takes care of calling aclocal before and after
libtoolize as it's done manually right now.
dev-lang/php releases are all fixed now, thanks for pointing this out!
Best regards, CHTEKK.
fixed for gphoto2
I've changed all misplaced elibtoolize calls to be called after autoconf,
libtoolize, or in general autoretooling.