From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Antoine Tenart <atenart@kernel.org>,
Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/libselinux: host-python3 needs SSL support
Date: Sun, 21 Dec 2025 13:49:17 +0100 [thread overview]
Message-ID: <2ff86f9df830a5675f399f2cfe828760@free.fr> (raw)
In-Reply-To: <20251217184822.3765937-1-bernd@kuhls.net>
Hi Bernd,
On 17/12/2025 19:48, Bernd Kuhls wrote:
> Buildroot commit 285097051d4a7dd821f01d15c705867f7e26c635 bumped
> python-pip to version 25.3, causing build errors when host-python3 was
> built without SSL support:
>
> WARNING: pip is configured with locations that require TLS/SSL,
> however the ssl module in Python is not available.
> [...]
> Could not fetch URL https://pypi.org/simple/setuptools/:
> There was a problem confirming the ssl certificate:
> HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded
> with url: /simple/setuptools/ (Caused by SSLError("Can't connect to
> HTTPS URL because the SSL module is not available.")) - skipping
> ERROR: Could not find a version that satisfies the requirement
> setuptools>=40.8.0 (from versions: none)
>
> Reverting the python-pip bump reveals the true cause of the build error
> by showing these messages:
>
> WARNING: pip is configured with locations that require TLS/SSL,
> however the ssl module in Python is not available.
> [...]
> DEPRECATION: Building 'selinux' using the legacy setup.py bdist_wheel
> mechanism, which will be removed in a future version. pip 25.3 will
> enforce this behaviour change. A possible replacement is to use the
> standardized build interface by setting the `--use-pep517` option,
> (possibly combined with `--no-build-isolation`), or adding a
> `pyproject.toml` file to the source tree of 'selinux'.
> Discussion can be found at https://github.com/pypa/pip/issues/6334
>
> Selecting BR2_PACKAGE_HOST_PYTHON3_SSL fixes the problem.
>
> Criu, the only other buildroot package using host-python-pip as
> dependency, already selects BR2_PACKAGE_HOST_PYTHON3_SSL.
>
> Fixes:
> https://autobuild.buildroot.net/results/fd6/fd6d3edd5f74d094621ac9fdb93db24520b7a6e3/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Hi Bernd,
While testing this patch, I observed two new new kind of build
errors. Those were reported in autobuilder. See for example:
https://autobuild.buildroot.org/results/953/953b8c6d7da0f150ec56760c4a3191e630c01381/build-end.log
https://autobuild.buildroot.org/results/a9b/a9bc288de3abefaa11f10d8ea93f425eff26ac71/build-end.log
It is possible those are related to the recent python
package updates.
The libselinux package might have a missing dependency
on host-python-setuptools.
Also I've seen that in libselinux.mk, $(PKG_PYTHON_SETUPTOOLS_ENV)
is passed to _MAKE_OPTS rather than _MAKE_ENV. Changing that worked
around those issues while testing.
You can reproduce those issues with the commands:
cat >.config <<EOF
BR2_aarch64=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_PACKAGE_PYTHON3=y
BR2_PACKAGE_LIBSELINUX=y
EOF
make olddefconfig
make libselinux
Since this SSL support in host-python3 is needed anyway, I applied
this patch to master, thanks.
Could you have a look the other issues, please? At the moment,
libselinux is
the biggest source of build failures:
https://lore.kernel.org/buildroot/694774fb.050a0220.99314.d33b@mx.google.com/T/#u
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-21 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 18:48 [Buildroot] [PATCH 1/1] package/libselinux: host-python3 needs SSL support Bernd Kuhls
2025-12-21 12:49 ` Julien Olivain via buildroot [this message]
2025-12-26 17:32 ` Thomas Petazzoni via buildroot
2025-12-27 14:59 ` Thomas Petazzoni via buildroot
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=2ff86f9df830a5675f399f2cfe828760@free.fr \
--to=buildroot@buildroot.org \
--cc=atenart@kernel.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
--cc=marcus.folkesson@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.