unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 47964@debbugs.gnu.org
Subject: bug#47964: webkitgtk-2.32.0 build fails
Date: Mon, 26 Apr 2021 14:25:28 -0400	[thread overview]
Message-ID: <87sg3cc38n.fsf@disroot.org> (raw)
In-Reply-To: <YIblbM2t3WJzhIhK@jasmine.lan>

Leo Famulari writes:
> Thanks for taking the time to perform all these builds; I'm sure they
> took a long time.

Thank you for helping me figure out how to build this package.

> I'm guessing that "--cores=2 --max-jobs=1" used fewer threads than the
> guix-daemon would normally choose by default on your computer? Like,
> maybe you have 4 cores / hyperthreads or something like that?

Yes that is correct. On the computer that was having trouble building
webkitgtk there are 4 cores and 8 threads and 8GiB of installed memory.




  parent reply	other threads:[~2021-04-26 18:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23  4:46 bug#47964: webkitgtk-2.32.0 build fails Bone Baboon via Bug reports for GNU Guix
2021-04-23 18:41 ` Leo Famulari
2021-04-23 20:11   ` Bone Baboon via Bug reports for GNU Guix
2021-04-23 20:25     ` Leo Famulari
2021-04-23 22:04       ` Leo Famulari
2021-04-26 13:58         ` Bone Baboon via Bug reports for GNU Guix
2021-04-26 16:08           ` Leo Famulari
2021-04-26 16:44             ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-26 17:19               ` Leo Famulari
2021-04-27 12:48                 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-26 18:25             ` Bone Baboon via Bug reports for GNU Guix [this message]
2021-04-23 21:37 ` Bone Baboon via Bug reports for GNU Guix
2021-04-26 14:52 ` bug#47964: Closing bug#47964 Bone Baboon via Bug reports for GNU Guix

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sg3cc38n.fsf@disroot.org \
    --to=bug-guix@gnu.org \
    --cc=47964@debbugs.gnu.org \
    --cc=bone.baboon@disroot.org \
    --cc=leo@famulari.name \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).