public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problem updating KDE breeze
Date: Sun, 21 Oct 2018 06:06:08 -0500	[thread overview]
Message-ID: <922d1828-1d4a-b58c-79bc-271e64475d19@gmail.com> (raw)
In-Reply-To: <CADtyuE6=tAU8MLGHy6ZM8jKwX5LHb_nqZxmFyp1FHcxF5gnYRQ@mail.gmail.com>

Franz Fellner wrote:
> Hi Philipp,
> the actual error really is missing.
> Can you use pastebin or something similar to upload the whole build.log?
>
> The number of cores may help to estimate the unmber of compilation
> units that still get built.
> Unfortunately not with cmake. It usually continues building targets
> that do not depend on the failed target.
> You may have to scroll up hundreds of lines.
>
> So, again: Please give us the complete buld.log!
>
> Thx
> Franz
>
>

Exactly.  Whenever a build fails, the compile phase generally, the first
error calls itself error 1.  Since I use Konsole here, I usually use the
Find function and search for "error 1" to help find it.  Then I scroll
backward until I see what really failed.  As you and I point out, it can
be a good ways back.  Usually in my case, it is less than 10 or 15 lines
since I have somewhat smaller settings.  Of course, depending on
settings, it can be hundreds of lines as you say. 

OP.  The original error is further up.  Otherwise, one would see error 1
in there somewhere.  It's sometimes hard to find but it's hiding in
there somewhere.  I'm not big on paste bin but if you can't find it,
posting a link to it is better than nothing.  As it is, it's going to be
hard to help since we can't see what failed, exactly.

Dale

:-)  :-) 


  reply	other threads:[~2018-10-21 11:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21  4:54 [gentoo-user] problem updating KDE breeze Philip Webb
2018-10-21  5:37 ` Dale
2018-10-21  8:29 ` Philip Webb
2018-10-21  8:49   ` Franz Fellner
2018-10-21 11:06     ` Dale [this message]
2018-10-22  4:15     ` Philip Webb
2018-10-22  4:48       ` Alexander Kapshuk
2018-10-22  4:53       ` [gentoo-user] problem updating KDE breeze : solved Philip Webb
2018-10-22  7:03         ` Franz Fellner
2018-10-22  7:45           ` Neil Bothwick
2018-10-22  8:08           ` Philip Webb

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=922d1828-1d4a-b58c-79bc-271e64475d19@gmail.com \
    --to=rdalek1967@gmail.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