From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] =dev-lang/spidermonkey-60.5.2_p0-r4 fails @world update
Date: Fri, 19 Jun 2020 12:57:27 -0400 [thread overview]
Message-ID: <YHQ4SNY7.OTL6QPI4.22YZH2X7@OMPCK2O5.FMIKRSMI.KES53HMR> (raw)
In-Reply-To: <20200619161054.GA3389@imap.gmx.com>
On 2020.06.19 12:10, urpion@gmx.com wrote:
> On Fri, Jun 19, 2020 at 04:52:30PM +0100, Michael wrote:
> > On Friday, 19 June 2020 16:35:27 BST urpion@gmx.com wrote:
> > > On Fri, Jun 19, 2020 at 09:45:59AM -0500, Dale wrote:
> > > > Jack wrote:
> > > > > Not far enough back. You need to show the actual error, not
> the line
> > > > > "Error1:" which gets printed after the error.
> > > >
> > > > And depending on the number of cores/threads and other emerge
> settings,
> > > > it can be a dozen, two dozen lines or sometimes even further
> back than
> > > > that. With CPUs having a dozen or so cores/threads, it's
> amazing that
> > > > some stuff compiles at all. Prime example, recent thread about
> Pam
> > > > updates.
> > > >
> > > > OP, if needed, tar the whole error log and attach it. Just
> don't post
> > > > it elsewhere and link to it tho. After a while, it's gone or a
> person
> > > > finds the log but not this thread with the solution.
> > > >
> > > > Dale
> > > >
> > > > :-) :-)
> > >
> > > Ah ha. Yes Thank you. Sorry, I've never been good with e-mail:-P
> >
> >
> > NP, did you get an OOM error in dmesg when this happened by any
> chance? You
> > don't seem to have much RAM, you have no swap and the number of
> jobs is
> > relatively high for memory hungry compiles.
> >
> > It could be a bug, but unless a report has been filed already in
> BGO to this
> > effect, I suggest you add a swapfile, enable it, and try again with
> > MAKEOPTS="-j1" or "-j2". Please ask if you need more detail.
>
>
> I was thinking about -j1. I tried -j4. I thought I didn't need swap
> with >=4GB
> of RAM, but it makes sense. My machine kinda crawls trying to build
> that
> package. Oh man, I'll have to re-partition:-(
Although it borders on a religious argument, many/most agree you always
need at least a small amount of swap.
https://wiki.gentoo.org/wiki/Knowledge_Base:Is_swap_space_really_necessary
You can also set up a swap file instead of a swap partition. You'll
have to search for instructions, I didn't find it quick enough to
include a link.
next parent reply other threads:[~2020-06-19 16:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200619161054.GA3389@imap.gmx.com>
2020-06-19 16:57 ` Jack [this message]
2020-06-19 23:07 ` [gentoo-user] =dev-lang/spidermonkey-60.5.2_p0-r4 fails @world update urpion
2020-06-20 7:57 ` Peter Humphrey
2020-06-22 1:48 ` Sean O'Myers
2020-06-22 2:09 ` Dale
[not found] <5eec6774.1c69fb81.7c1cf.736eSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-19 7:37 ` Dale
2020-06-19 10:15 ` urpion
2020-06-19 12:48 ` Jack
2020-06-19 14:45 ` Dale
2020-06-19 15:35 ` urpion
2020-06-19 15:52 ` Michael
2020-06-19 16:10 ` urpion
2020-06-19 16:55 ` Peter Humphrey
2020-06-19 17:08 ` Michael
2020-06-19 22:56 ` urpion
[not found] ` <5eece98e.1c69fb81.660a3.a90bSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-19 17:19 ` Dale
2020-06-19 23:04 ` urpion
2020-06-19 7:20 urpion
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=YHQ4SNY7.OTL6QPI4.22YZH2X7@OMPCK2O5.FMIKRSMI.KES53HMR \
--to=ostroffjh@users.sourceforge.net \
--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