I can't finish building of hal 0.5.7. It shows to me as following lines endlessly. ------- make[3]: Entering directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/examples'make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/examples' make[2]: Leaving directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/examples' Making all in po make[2]: Entering directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/po' cd .. \ && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/sh ./config.status config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing intltool commands config.status: executing default-1 commands make[2]: Leaving directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/po' make[2]: Entering directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/po' cd .. \ && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/sh ./config.status config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing intltool commands config.status: executing default-1 commands make[2]: Leaving directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/po' make[2]: Entering directory `/var/tmp/portage/hal-0.5.7/work/hal-0.5.7/po' cd .. \ && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/sh ./config.status ----------- When I drop out the following line, it builds successfully, but I'm not sure if it is correct. --- hal-0.5.7.ebuild 2006-03-18 18:31:46.000000000 -0800 +++ /usr/local/portage/sys-apps/hal/hal-0.5.7-r1.ebuild 2006-03-18 22:20:53.070000000 -0800 @@ -111,7 +111,7 @@ # allow plugdev group people to mount epatch "${FILESDIR}"/${PN}-0.5.7-plugdev-allow-send.patch - eautoreconf + #eautoreconf }
That's something screwy with autotools on your system. But as it turns out I dunno why the Gnome guys added eautoreconf, it's not needed.
*** Bug 126812 has been marked as a duplicate of this bug. ***
Maybe someone should fix it in portage, because I just got the same thing...
It's marked fixed and was fixed over an hour before your comment. emerge --sync