public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cross-emerge dev-lang/spidermonkey fails without obvious error
Date: Tue, 8 Dec 2020 00:31:54 +0000	[thread overview]
Message-ID: <20201208003154.2b2d2819@digimed.co.uk> (raw)
In-Reply-To: <ef345971-160c-feba-307d-f7aaaf1f3c4b@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

On Mon, 7 Dec 2020 17:37:00 -0600, Dale wrote:

> >> Back when CPUs were single core, the error messages were fairly
> >> close to the bottom.  After all, it was running one or two pieces of
> >> code at a time.  With newer multi-core/threaded CPUs, that message
> >> gets further back the more cores/threads you have.   
> > Which is why it helps to repeat the emerge attempt with
> > MAKEOPTS="-j1". Sometimes that in itself fixes the issue, in which
> > case you can report a bug. Even if the build still fails, it is much
> > easier to see the symptoms of the problem when it is not all mixed in
> > with the output from successful operations.

> That is true too.  There is the occasional failure that -j1 fixes but I
> haven't seen that in quite a long time.  To save time tho, it might be
> wise to at least try it but I wouldn't hold my breath or anything. 

-j1 fixing the problem is just the occasional side benefit, the main
reason for doing it is to produce more readable error output.


-- 
Neil Bothwick

My Go this  amn keyboar  oesn't have any  's.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-12-08  0:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07  8:14 [gentoo-user] cross-emerge dev-lang/spidermonkey fails without obvious error Britaliope
2020-12-07  8:40 ` netfab
2020-12-07 11:13   ` Britaliope
2020-12-07 20:48     ` Dale
2020-12-07 22:31       ` Neil Bothwick
2020-12-07 23:37         ` Dale
2020-12-08  0:31           ` Neil Bothwick [this message]
2020-12-08  1:44             ` Dale

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=20201208003154.2b2d2819@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