unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 51564-done@debbugs.gnu.org, 51559-done@debbugs.gnu.org,
	51555-done@debbugs.gnu.org
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: bug#51555: bug#51564: [PATCH] gnu: webkitgtk: Fix configure failures.
Date: Wed, 03 Nov 2021 14:09:19 -0400	[thread overview]
Message-ID: <878ry5m7px.fsf@netris.org> (raw)
In-Reply-To: <87fssdn1xu.fsf@netris.org>

FYI, I pushed commit 9d3a5ddc2700aa099bb1bf9c5e8b3062445b907a to
'master', which fixes the webkitgtk-2.34.1 build on x86_64-linux.  In
addition to the fixes already shown in Liliana's proposed patch,
9d3a5ddc27 also arranges to use clang-11 for compilation.

Unfortunately, the build fails on i686-linux, which is the only system
other than x86_64-linux where webkitgtk-2.32.4 was successfully built.

Note that I tried clang-11 first, because upstream WebKit surely uses
clang for compilation, and it works for building IceCat on Guix, so I
had it hunch that it was a good bet.  However, it would be good to now
try compiling webkitgtk-2.34.1 with a newer version of GCC.  It's
possible that might fix the build on i686-linux.

Anyway, I'm closing this bug.  I'll open another bug to track the
i686-linux issue.

     Thanks,
       Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.




  parent reply	other threads:[~2021-11-03 18:12 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
2021-11-03 18:09               ` Mark H Weaver [this message]
2021-11-03 19:21                 ` bug#51555: " 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=878ry5m7px.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=51555-done@debbugs.gnu.org \
    --cc=51559-done@debbugs.gnu.org \
    --cc=51564-done@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    /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).