From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Leo Famulari <leo@famulari.name>, Mark H Weaver <mhw@netris.org>
Cc: 51564@debbugs.gnu.org, 51555@debbugs.gnu.org,
51559@debbugs.gnu.org, 51591@debbugs.gnu.org
Subject: bug#51559: bug#51564: [PATCH] gnu: webkitgtk: Fix configure failures.
Date: Thu, 04 Nov 2021 17:49:40 +0100 [thread overview]
Message-ID: <afcd05215210f94af49f78d7bf02e7769e5afaa0.camel@gmail.com> (raw)
In-Reply-To: <YYQAgDBYfqPGUk6K@jasmine.lan>
Am Donnerstag, den 04.11.2021, 11:47 -0400 schrieb Leo Famulari:
> On Thu, Nov 04, 2021 at 08:57:18AM -0400, Mark H Weaver wrote:
> > Although the WebKitGTK package itself built successfully using GCC
> > 11,
> > the switch to GCC 11 caused many failures in programs that use
> > WebKitGTK. For example:
>
> Should we just revert the WebKitGTK upgrade for now?
SGTM. Can someone check whether it builds fine with GCC 10 on c-u-
frozen?
next prev parent reply other threads:[~2021-11-04 16:50 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 ` 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 ` Liliana Marie Prikler [this message]
2021-11-04 22:23 ` 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=afcd05215210f94af49f78d7bf02e7769e5afaa0.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=51555@debbugs.gnu.org \
--cc=51559@debbugs.gnu.org \
--cc=51564@debbugs.gnu.org \
--cc=51591@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).