Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kadir Yilmaz <kadir.c.yilmaz@gmail.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Julien Corjon <corjon.j@ecagroup.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/qt5webengine-chromium: fix python3.11 build errors
Date: Mon, 15 Jul 2024 12:18:00 +0200	[thread overview]
Message-ID: <20240715121800.7aa996cf@windsurf> (raw)
In-Reply-To: <20231025205233.1925727-1-kadir.c.yilmaz@gmail.com>

Hello Kadir,

On Wed, 25 Oct 2023 22:52:33 +0200
Kadir Yilmaz <kadir.c.yilmaz@gmail.com> wrote:

> qt5webengine fails to build due to changes introduced in python3.11:
> 
> - [864/23192] ACTION //services/metrics/public/cpp:gen_ukm_builders(/ho
>   me/vagrant/output_raspberrypi3_qt5we/build/qt5webengine-5.15.8/src/to
>   olchain:target)
>   ...
>   re.error: global flags not at the start of the expression at position 1
> 
>     https://docs.python.org/3.11/library/re.html
>     (?aiLmsux)
>     Changed in version 3.11: This construction can only be used at the
>     start of the expression.
> 
> - [3742/22323] ACTION //chrome/app:chromium_strings_grit(/home/vagrant/
>   output_raspberrypi3_qt5we/build/qt5webengine-5.15.8/src/toolchain:tar
>   get)
>   ...
>   ValueError: invalid mode: 'rU'
> 
>     open(), io.open(), codecs.open() and fileinput.FileInput no longer
>     accept 'U' (“universal newline”) in the file mode. In Python 3,
>     “universal newline” mode is used by default whenever a file is
>     opened in text mode, and the 'U' flag has been deprecated since
>     Python 3.3. The newline parameter to these functions controls how
>     universal newlines work. (Contributed by Victor Stinner in bpo-37330.)
> 
> Signed-off-by: Kadir Yilmaz <kadir.c.yilmaz@gmail.com>
> ---
>  ...x-build-tools-to-run-with-python3.11.patch | 72 +++++++++++++++++++
>  1 file changed, 72 insertions(+)
>  create mode 100644 package/qt5/qt5webengine-chromium/0003-Fix-build-tools-to-run-with-python3.11.patch

So I did not really apply your patch as-is, because instead I
backported fixes from Chromium upstream instead. As said in another
patch, I just pushed 13 commits that fix a number of things in
qt5webengine, and that allow a successful build of this configuration:

BR2_aarch64=y
BR2_ARM_FPU_VFPV3D16=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SWRAST=y
BR2_PACKAGE_MESA3D_OPENGL_EGL=y
BR2_PACKAGE_MESA3D_OPENGL_ES=y
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5WEBENGINE=y

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-07-15 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 20:52 [Buildroot] [PATCH 1/1] package/qt5webengine-chromium: fix python3.11 build errors Kadir Yilmaz
2024-06-06  9:46 ` Yann E. MORIN
2024-07-15 10:18 ` Thomas Petazzoni via buildroot [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240715121800.7aa996cf@windsurf \
    --to=buildroot@buildroot.org \
    --cc=corjon.j@ecagroup.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=kadir.c.yilmaz@gmail.com \
    --cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox