Created
July 13, 2012 14:13
-
-
Save zjhui/3105122 to your computer and use it in GitHub Desktop.
error-message
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
make[6]: *** [plugin-container] Error 1 | |
make[6]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10/obj-i686-pc-linux-gnu/ipc/app' | |
make[5]: *** [tools] Error 2 | |
make[5]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10/obj-i686-pc-linux-gnu/ipc' | |
make[4]: *** [tools_tier_platform] Error 2 | |
make[4]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10/obj-i686-pc-linux-gnu' | |
make[3]: *** [tier_platform] Error 2 | |
make[3]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10/obj-i686-pc-linux-gnu' | |
make[2]: *** [default] Error 2 | |
make[2]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10/obj-i686-pc-linux-gnu' | |
make[1]: *** [realbuild] Error 2 | |
make[1]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10' | |
make: *** [build] Error 2 | |
emake failed | |
* ERROR: www-client/firefox-10.0.5 failed (compile phase): | |
* emake failed | |
* | |
* Call stack: | |
* ebuild.sh, line 85: Called src_compile | |
* environment, line 6852: Called die | |
* The specific snippet of code: | |
* CC="$(tc-getCC)" CXX="$(tc-getCXX)" LD="$(tc-getLD)" MOZ_MAKE_FLAGS="${MAKEOPTS}" emake -f client.mk || die "emake failed"; | |
* | |
* If you need support, post the output of `emerge --info '=www-client/firefox-10.0.5'`, | |
* the complete build log and the output of `emerge -pqv '=www-client/firefox-10.0.5'`. | |
/usr/lib/portage/bin/isolated-functions.sh: line 214: wait: `emake failed': not a pid or valid job spec | |
* The complete build log is located at '/var/tmp/portage/www-client/firefox-10.0.5/temp/build.log'. | |
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-10.0.5/temp/environment'. | |
* Working directory: '/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10' | |
* S: '/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10' | |
>>> Failed to emerge www-client/firefox-10.0.5, Log file: | |
>>> '/var/tmp/portage/www-client/firefox-10.0.5/temp/build.log' | |
* Messages for package www-client/firefox-10.0.5: | |
* You are enabling official branding. You may not redistribute this build | |
* to any users on your network or the internet. Doing so puts yourself into | |
* a legal problem with Mozilla Foundation | |
* You can disable it by emerging firefox _with_ the bindist USE-flag | |
* There is NOT at least 4 gibibytes disk space at "/var/tmp/portage/www-client/firefox-10.0.5/temp" | |
* | |
* Space constrains set in the ebuild were not met! | |
* The build will most probably fail, you should enhance the space | |
* as per failed tests. | |
* | |
* ERROR: www-client/firefox-10.0.5 failed (compile phase): | |
* emake failed | |
* | |
* Call stack: | |
* ebuild.sh, line 85: Called src_compile | |
* environment, line 6852: Called die | |
* The specific snippet of code: | |
* CC="$(tc-getCC)" CXX="$(tc-getCXX)" LD="$(tc-getLD)" MOZ_MAKE_FLAGS="${MAKEOPTS}" emake -f client.mk || die "emake failed"; | |
* | |
* If you need support, post the output of `emerge --info '=www-client/firefox-10.0.5'`, | |
* the complete build log and the output of `emerge -pqv '=www-client/firefox-10.0.5'`. | |
* The complete build log is located at '/var/tmp/portage/www-client/firefox-10.0.5/temp/build.log'. | |
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-10.0.5/temp/environment'. | |
* Working directory: '/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10' | |
* S: '/var/tmp/portage/www-client/firefox-10.0.5/work/mozilla-esr10' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment