public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: urpion@gmx.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] =dev-lang/spidermonkey-60.5.2_p0-r4 fails @world update
Date: Sat, 20 Jun 2020 01:35:27 +1000	[thread overview]
Message-ID: <20200619153324.GA3316@imap.gmx.com:993> (raw)
In-Reply-To: <3a413a69-9cdd-d69b-ba43-919e454e6500@gmail.com>

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

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

[-- Attachment #2: build.log.tar.gz --]
[-- Type: application/octet-stream, Size: 71584 bytes --]

  reply	other threads:[~2020-06-19 15:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5eec6774.1c69fb81.7c1cf.736eSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-19  7:37 ` [gentoo-user] =dev-lang/spidermonkey-60.5.2_p0-r4 fails @world update 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 [this message]
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
2020-06-20  3:18         ` [gentoo-user] Re: [SOLVED] " urpion
2020-06-20 10:29       ` Michael
     [not found]     ` <5eece98e.1c69fb81.660a3.a90bSMTPIN_ADDED_BROKEN@mx.google.com>
2020-06-19 17:19       ` [gentoo-user] " Dale
2020-06-19 23:04         ` urpion
     [not found] <20200619161054.GA3389@imap.gmx.com>
2020-06-19 16:57 ` Jack
2020-06-19 23:07   ` urpion
2020-06-20  7:57   ` Peter Humphrey
2020-06-22  1:48     ` Sean O'Myers
2020-06-22  2:09       ` Dale
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='20200619153324.GA3316@imap.gmx.com:993' \
    --to=urpion@gmx.com \
    --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