| 1 |
On 03/15/2018 12:29 PM, Neil Bothwick wrote: |
| 2 |
> On Thu, 15 Mar 2018 11:40:13 -0400, Walter Dnes wrote: |
| 3 |
> |
| 4 |
>>> ninja: build stopped: subcommand failed. |
| 5 |
>>> * ERROR: net-libs/webkit-gtk-2.18.6::gentoo failed (compile phase): |
| 6 |
>>> * ninja -v -j5 -l8 failed |
| 7 |
>> |
| 8 |
>> One option that sometimes cures mysterious failures is to do the build |
| 9 |
>> with... |
| 10 |
>> MAKEOPTS="-j1" |
| 11 |
>> Yes, the build takes longer, but it may actually build. Remember to |
| 12 |
>> set the option back to normal value after experimenting. |
| 13 |
> |
| 14 |
> You can set it on the command line for that build only |
| 15 |
> |
| 16 |
> MAKEOPTS="-j1" emerge whatever |
| 17 |
> |
| 18 |
> I too find that it can help builds that otherwise fail, even when it |
| 19 |
> doesn't, the make output gives a better idea of the failure point when |
| 20 |
> parallel builds are not cluttering it up. |
| 21 |
> |
| 22 |
> If the build log is that big, either compress it or just post the last |
| 23 |
> 100 lines. The error message you posted doesn't really say much more than |
| 24 |
> "it broke". |
| 25 |
|
| 26 |
Thanks Walter and Neil, Yes, that was the case not enough RAM, |
| 27 |
MAKEOPTS="-j1" fixed the problem. |
| 28 |
|
| 29 |
Though, it was sloooow. On Intel Quad core CPU and 4MB of RAM it took |
| 30 |
over 7-hours to compile it. |
| 31 |
I guess I need more RAM. |
| 32 |
|
| 33 |
-- |
| 34 |
Thelma |
Archives