unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Mark H Weaver <mhw@netris.org>, Leo Famulari <leo@famulari.name>,
	51564@debbugs.gnu.org
Subject: bug#51564: [PATCH] gnu: webkitgtk: Fix configure failures.
Date: Wed, 03 Nov 2021 18:52:56 +0100	[thread overview]
Message-ID: <8da77d934fae732fd5a3cbec269e2bd6258a5f63.camel@gmail.com> (raw)
In-Reply-To: <87fssdn1xu.fsf@netris.org>

Am Mittwoch, den 03.11.2021, 03:16 -0400 schrieb Mark H Weaver:
> In the case, upstream's upstream (WebKit) is Apple, which I guess
> uses some version of clang for compilation.  I'm currently trying to
> build WebKitGTK with clang-11, and so far it looks hopeful.  It has
> gotten beyond the point where it failed before, anyway.
I don't think we want to use Clang for WebKit, even if Apple does. 
Either way...

> I do not yet know whether it will ultimately succeed, but I went
> ahead and pushed my preliminary patch to the 'gnuzilla-updates'
> branch. (Admittedly, it's a slight abuse of that branch, but this was
> the most expedient way for me to ask the Berlin build farm to try
> building WebKitGTK and its dependents on the 'master' branch.)
> 
> If it turns out to work, feel free to push the commit to 'master' on
> my behalf (with the "UNTESTED: " prefix removed from the log, of
> course).
It builds for x86_64, but fails for i686.  I haven't checked the other
systems, perhaps they finished during my commute, but I'm pretty sure
that means no webkit for a large amount of users.

Regards,
Liliana





  reply	other threads:[~2021-11-03 17:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  6:03 bug#51564: Old libsoup package failing system reconfigure Disseminate Dissent via Bug reports for GNU Guix
2021-11-02  6:09 ` bug#51564: Try adding -DUSE_SOUP2 Jacob Hrbek
2021-11-02  6:17 ` bug#51564: (No Subject) Jacob Hrbek
2021-11-02 10:04 ` bug#51564: [PATCH] gnu: webkitgtk: Fix configure failures Liliana Marie Prikler
2021-11-02 13:45   ` Mark H Weaver
2021-11-02 14:10   ` Leo Famulari
2021-11-02 16:08     ` Mark H Weaver
2021-11-02 16:15       ` Liliana Marie Prikler
2021-11-02 17:31         ` Mark H Weaver
2021-11-02 18:10           ` Liliana Marie Prikler
2021-11-03  7:16             ` Mark H Weaver
2021-11-03 17:52               ` Liliana Marie Prikler [this message]
2021-11-03 18:09               ` bug#51555: " Mark H Weaver
2021-11-03 19:21                 ` Liliana Marie Prikler
2021-11-03 21:46                   ` Mark H Weaver
2021-11-04  8:29                   ` bug#51559: " Mark H Weaver
2021-11-04 12:57                     ` Mark H Weaver
2021-11-04 15:47                       ` bug#51555: " Leo Famulari
2021-11-04 16:49                         ` bug#51559: " Liliana Marie Prikler
2021-11-04 22:23                         ` bug#51555: " Mark H Weaver

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=8da77d934fae732fd5a3cbec269e2bd6258a5f63.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=51564@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=mhw@netris.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).