1 |
On 01/11/2014 02:32 PM, Tom Wijsman wrote: |
2 |
> On Sat, 11 Jan 2014 17:16:36 -0500 |
3 |
> Andrew Penhorwood <andrew@××××××××.com> wrote: |
4 |
> |
5 |
>> * ERROR: sys-devel/binutils-2.23.2::gentoo failed (compile phase): |
6 |
>> * emake failed |
7 |
>> * |
8 |
>> * Call stack: |
9 |
>> * ebuild.sh, line 93: Called src_compile |
10 |
>> * environment, line 2823: Called toolchain-binutils_src_compile |
11 |
>> * environment, line 3514: Called die |
12 |
>> * The specific snippet of code: |
13 |
>> * emake all || die "emake failed"; |
14 |
>> * |
15 |
>> * If you need support, post the output of `emerge --info |
16 |
>> '=sys-devel/binutils-2.23.2::gentoo'`, |
17 |
>> * the complete build log and the output of `emerge -pqv |
18 |
>> '=sys-devel/binutils-2.23.2::gentoo'`. |
19 |
>> * The complete build log is located at |
20 |
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/build.log'. |
21 |
>> * The ebuild environment file is located at |
22 |
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/environment'. |
23 |
>> * Working directory: |
24 |
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/build' |
25 |
>> * S: |
26 |
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2' |
27 |
> |
28 |
> Can you please file a bug about this at https://bugs.gentoo.org and |
29 |
> attach all the requested information? At the very least comment with |
30 |
> the output of `emerge --info` and attach the complete build.log. |
31 |
|
32 |
I was about to reply to Andrew that running an emerge with -j1 can make |
33 |
the build log easier to scan for errors, and can sometimes even prevent |
34 |
build errors in certain packages. |
35 |
|
36 |
[OT] |
37 |
Tom, I very rudely forgot to thank you for your reply to my recent post |
38 |
about layman. So...thank you! |
39 |
|
40 |
As a group we tend to be tough on devs who actually answer questions here |
41 |
even though we really are harmless. No, really, we are, honest, just ask |
42 |
us. |