I will try the -j1. This is a VM that is initially setup my Linode.com.
Andrew
On 1/11/2014 6:19 PM, walt wrote:
On 01/11/2014 02:32 PM, Tom Wijsman wrote:
On Sat, 11 Jan 2014 17:16:36 -0500
Andrew Penhorwood <[email protected]> wrote:
* ERROR: sys-devel/binutils-2.23.2::gentoo failed (compile phase):
* emake failed
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 2823: Called toolchain-binutils_src_compile
* environment, line 3514: Called die
* The specific snippet of code:
* emake all || die "emake failed";
*
* If you need support, post the output of `emerge --info
'=sys-devel/binutils-2.23.2::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=sys-devel/binutils-2.23.2::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/sys-devel/binutils-2.23.2/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-devel/binutils-2.23.2/temp/environment'.
* Working directory:
'/var/tmp/portage/sys-devel/binutils-2.23.2/work/build'
* S:
'/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2'
Can you please file a bug about this at https://bugs.gentoo.org and
attach all the requested information? At the very least comment with
the output of `emerge --info` and attach the complete build.log.
I was about to reply to Andrew that running an emerge with -j1 can make
the build log easier to scan for errors, and can sometimes even prevent
build errors in certain packages.
[OT]
Tom, I very rudely forgot to thank you for your reply to my recent post
about layman. So...thank you!
As a group we tend to be tough on devs who actually answer questions here
even though we really are harmless. No, really, we are, honest, just ask
us.
--
Andrew Penhorwood
ColdBits, LLC
www.coldbits.com
[email protected]
740-358-9129
