From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: John Kehayias <john.kehayias@protonmail.com>, 67829@debbugs.gnu.org
Subject: bug#67829: qtwebengine new failure on i686
Date: Tue, 19 Dec 2023 11:46:37 -0500 [thread overview]
Message-ID: <87edfi5edu.fsf@gmail.com> (raw)
In-Reply-To: <ZX3frUhH_OMwr8T1@3900XT> (Efraim Flashner's message of "Sat, 16 Dec 2023 19:34:37 +0200")
Hi Efraim,
Efraim Flashner <efraim@flashner.co.il> writes:
[...]
> Upstream chromium removed support for i686 so that's why it's failing.
>
> https://sources.debian.org/src/qt6-webengine/6.6.1%2Bdfsg-1/debian/patches/support-i386.patch/
> https://sources.debian.org/src/qt6-webengine/6.6.1%2Bdfsg-1/debian/patches/disable_32bit_node_check.patch/
> https://sources.debian.org/src/qt6-webengine/6.6.1%2Bdfsg-1/debian/patches/compressing_files.patch/
>
> There's two or three patches we can add to re-enable builds on i686, or
> we can mark it as unsupported. I don't have a strong opinion either
> way.
If Debian already did the hard work, the best option seems to use their
patches to enable the build on i686 at least :-). If it becomes to hard
to maintain and they lag on upstream, we could reconsider just marking
it as unsupported.
--
Thanks,
Maxim
prev parent reply other threads:[~2023-12-19 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 20:33 bug#67829: qtwebengine new failure on i686 Maxim Cournoyer
2023-12-15 6:04 ` John Kehayias via Bug reports for GNU Guix
2023-12-16 17:34 ` Efraim Flashner
2023-12-19 16:46 ` Maxim Cournoyer [this message]
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=87edfi5edu.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=67829@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=john.kehayias@protonmail.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).