I'm not sure what is wrong, but since xulrunner appears to be common denominator, i have listed it here. Latest emerge -uD world tried to emerge xulrunner, versions 1.8.1.18-r1 and xulrunner-1.9.0.4-r1, both of which failed to emerge. After that I seen that I couldn't emerge even existing existing 1.8.1.17 and 1.9.0.3. They die with the message: * Applying various patches (bugfixes/updates) ... * 000_flex-configure-LANG.patch ... [ ok ] * 001-xul_gentoo_install_dirs.patch ... [ ok ] * 002-bzXXX_pc_honour_system_nspr_nss.patch ... [ ok ] * 055_firefox-2.0_gfbsd-pthreads.patch ... [ ok ] * 063_firefox-rpath-3.patch ... [ ok ] * 064_firefox-nsplugins-v3.patch ... [ ok ] * 068_firefox-nss-gentoo-fix.patch ... [ ok ] * 100-system-hunspell-corrections.patch ... [ ok ] * 800-bsd_include.patch ... [ ok ] * Done with patching * Running eautoreconf in '/var/tmp/portage/net-libs/xulrunner-1.9.0.4-r1/work/mozilla' ... * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/net-libs/xulrunner-1.9.0.4-r1/temp/autoconf-29969.out * * ERROR: net-libs/xulrunner-1.9.0.4-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 5096: Called eautoreconf * environment, line 1357: Called eautoconf * environment, line 1300: Called autotools_run_tool 'autoconf' * environment, line 717: Called die * The specific snippet of code: * die "Failed Running $1 !"; * The die message: * Failed Running autoconf ! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/net-libs:xulrunner-1.9.0.4-r1:20081116-215825.log'. * The ebuild environment file is located at '/var/tmp/portage/net-libs/xulrunner-1.9.0.4-r1/temp/environment'. * !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.10" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="" and of course, the output of emerge --info >>> Failed to emerge net-libs/xulrunner-1.9.0.4-r1, Log file: >>> '/var/log/portage/net-libs:xulrunner-1.9.0.4-r1:20081116-215825.log' I have tried to emerge xulrunners listed direct dependencies and autoconf since ebuild says something about eautoreconfig failure. Results are exactly the same as before. Reproducible: Always
Created attachment 172110 [details] emerge --info output...
My standard comment: read what you've posted and follow those suggestions.
Created attachment 172131 [details] log file as requested in ebuild...
Created attachment 172132 [details] eclass debug log from the same map
Created attachment 172133 [details] file that should contain "complete build log"
Created attachment 172134 [details] complete build log
Which versions of autoconf you've got ? Do you have following files: /usr/share/autoconf/autoconf.m4 /usr/share/autoconf/autoconf/autoconf.m4 ?
Sorry, I've missed your 'emerge --info'.
(In reply to comment #7) > Do you have following files: > /usr/share/autoconf/autoconf.m4 No. "equery belongs /usr/share/autoconf/autoconf.m4" sys it belongs to autoconf-2.13. Silly me. Didn't think to re-emerge all existing versions, just latest. emerge =autoconf-2.13 fixed it. Everything now builds fine. Thanks.
firefox 3.0.7 was wiped out of the portage tree, but firefox 3.0.8 needs >=net-libs/xulrunner-1.9.0.8 if a downgrade to version 2 of firefox is not wanted, a "workaround" is to disable the xulrunner use flag for www-client/mozilla-firefox
