Red Hat Bugzilla – Bug 434382
blam failed massrebuild attempt for GCC 4.3
Last modified: 2013-01-09 22:10:05 EST
This is an automatically filed bug for a failed rebuild attempt for GCC 4.3.
Please verify why this build failed and fix it.
Exit code was 1, check the build.log for the failed buildArch task.
Configure failure for PPC:
checking which mozilla to use... configure: error: no mozilla installation found
error: Bad exit status from /var/tmp/rpm-tmp.14312 (%build)
This is not a problem with gcc 4.3 per se, it's a problem with port to using
xulrunner rather than firefox-devel. This was fixed at some point, and is now
unfixed (will check for old bug).
Can't update to latest blam which may fix the xulrunner problem because
gnome-sharp is too low.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
*** Bug 449619 has been marked as a duplicate of this bug. ***
Still a problem in rawhide, switching components. Trying some new builds now
(broken deps in F-9 too).
OK, so the xulrunner check doesn't seem to be working correctly:
/configure: line 22066: test: too many arguments
checking for MOZILLA_COMPONENT...
configure: error: Package requirements (xulrunner-gtkmozembed >= 1.8
xulrunner-xpcom >= 1.8) were not met:
No package 'xulrunner-gtkmozembed' found
No package 'xulrunner-xpcom' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables MOZILLA_COMPONENT_CFLAGS
and MOZILLA_COMPONENT_LIBS to avoid the need to call pkg-config.
So the current xulrunner patch doesn't appear to be sufficient. I think the
xulrunner-devel library is called something different in the Fedora library,
libxul-xpcom or somesuch. An expert on gecko/xulrunner might know what exactly
is needed here.
blam-1.8.5-1.fc9 has been submitted as an update for Fedora 9
blam-1.8.5-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.