1 |
Kaizu Shibata wrote: |
2 |
> |
3 |
> Dale: |
4 |
>> Kaizu Shibata wrote: |
5 |
>>> I'm having trouble with an update. I can't seem to build the new gcc, |
6 |
>>> and I don't understand the error. For some reason, a process has been |
7 |
>>> killed. I do not know why this is. |
8 |
>>> |
9 |
>>> make[3]: *** [Makefile:2176: s-attrtab] Killed |
10 |
>>> make[3]: *** Waiting for unfinished jobs.... |
11 |
>>> /bin/bash |
12 |
>>> /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0/gcc/../move-if-change |
13 |
>>> tmp-automata.c insn-automata.c |
14 |
>>> echo timestamp > s-automata |
15 |
>>> rm gcc.pod |
16 |
>>> make[3]: Leaving directory |
17 |
>>> '/var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/build/gcc' |
18 |
>>> make[2]: *** [Makefile:4367: all-stage1-gcc] Error 2 |
19 |
>>> make[2]: Leaving directory |
20 |
>>> '/var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/build' |
21 |
>>> make[1]: *** [Makefile:18753: stage1-bubble] Error 2 |
22 |
>>> make[1]: Leaving directory |
23 |
>>> '/var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/build' |
24 |
>>> make: *** [Makefile:19085: bootstrap-lean] Error 2 |
25 |
>>> * ERROR: sys-devel/gcc-5.4.0-r3::gentoo failed (compile phase): |
26 |
>>> * emake failed |
27 |
>>> * |
28 |
>>> * If you need support, post the output of `emerge --info |
29 |
>>> '=sys-devel/gcc-5.4.0-r3::gentoo'`, |
30 |
>>> * the complete build log and the output of `emerge -pqv |
31 |
>>> '=sys-devel/gcc-5.4.0-r3::gentoo'`. |
32 |
>>> * The complete build log is located at |
33 |
>>> '/var/tmp/portage/sys-devel/gcc-5.4.0-r3/temp/build.log'. |
34 |
>>> * The ebuild environment file is located at |
35 |
>>> '/var/tmp/portage/sys-devel/gcc-5.4.0-r3/temp/environment'. |
36 |
>>> * Working directory: '/var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/build' |
37 |
>>> * S: '/var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-5.4.0' |
38 |
>>> * |
39 |
>>> * Please include |
40 |
>>> /var/tmp/portage/sys-devel/gcc-5.4.0-r3/work/gcc-build-logs.tar.bz2 in |
41 |
>>> your bug report. |
42 |
>>> |
43 |
>> |
44 |
>> You need to look back further. There is a error further up the output. |
45 |
>> Look for Error 1 and then go back a little further still. Sometimes it |
46 |
>> can start a dozen or more lines back. |
47 |
>> |
48 |
>> Dale |
49 |
>> |
50 |
>> :-) :-) |
51 |
> There was no error in the build log, however I found an out of memory |
52 |
> error in dmesg. I've created a swap file. |
53 |
> |
54 |
> |
55 |
|
56 |
I saw error 2, usually there is a error 1. Sometimes its hard to find |
57 |
though. It can be buried. That said, if it ran out of memory, it may |
58 |
not be there anymore. It may have burped it out. lol |
59 |
|
60 |
I hate when I run out of memory. I have 16GBs here and I still run |
61 |
short at times. :/ Either way, glad you figured it out and hope it got |
62 |
you back on the right path again. |
63 |
|
64 |
Dale |
65 |
|
66 |
:-) :-) |