unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 47964@debbugs.gnu.org
Subject: bug#47964: webkitgtk-2.32.0 build fails
Date: Fri, 23 Apr 2021 18:04:51 -0400	[thread overview]
Message-ID: <YINEg2eXWDQCGjmW@jasmine.lan> (raw)
In-Reply-To: <YIMtIw1L9nihBasO@jasmine.lan>

On Fri, Apr 23, 2021 at 04:25:07PM -0400, Leo Famulari wrote:
> To be continued...

Well, I think that all that was a red herring.

I googled your error message:

"No rule to make target 'JavaScriptCore-4.0.gir', needed by 'WebKit2-4.0.gir'.  Stop."

And there are very many results, from many distros, and the answer in
all cases seems to be "Don't build this package with -j1".

I have to agree with that :) It's weird that a build fails with -j1, but
this build takes a long time even with many cores.

The upstream bug report:

https://bugs.webkit.org/show_bug.cgi?id=195251




  reply	other threads:[~2021-04-23 22:06 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 [this message]
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
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=YINEg2eXWDQCGjmW@jasmine.lan \
    --to=leo@famulari.name \
    --cc=47964@debbugs.gnu.org \
    --cc=bone.baboon@disroot.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.
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).