From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] webkit-gtk-2.18.6 failed (compile phase)
Date: Thu, 15 Mar 2018 18:29:31 +0000 [thread overview]
Message-ID: <20180315182931.0813dc41@digimed.co.uk> (raw)
In-Reply-To: <20180315154013.GA3476@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Thu, 15 Mar 2018 11:40:13 -0400, Walter Dnes wrote:
> > ninja: build stopped: subcommand failed.
> > * ERROR: net-libs/webkit-gtk-2.18.6::gentoo failed (compile phase):
> > * ninja -v -j5 -l8 failed
>
> One option that sometimes cures mysterious failures is to do the build
> with...
> MAKEOPTS="-j1"
> Yes, the build takes longer, but it may actually build. Remember to
> set the option back to normal value after experimenting.
You can set it on the command line for that build only
MAKEOPTS="-j1" emerge whatever
I too find that it can help builds that otherwise fail, even when it
doesn't, the make output gives a better idea of the failure point when
parallel builds are not cluttering it up.
If the build log is that big, either compress it or just post the last
100 lines. The error message you posted doesn't really say much more than
"it broke".
--
Neil Bothwick
Top Oxymorons Number 1: Microsoft Works
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-15 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 4:29 [gentoo-user] webkit-gtk-2.18.6 failed (compile phase) thelma
2018-03-15 15:40 ` Walter Dnes
2018-03-15 18:29 ` Neil Bothwick [this message]
2018-03-15 20:57 ` [gentoo-user] [SOLVED] " thelma
2018-03-15 21:08 ` J. Roeleveld
2018-05-06 22:02 ` Mart Raudsepp
2018-03-15 21:05 ` [gentoo-user] " J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180315182931.0813dc41@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox