From: David Jander <david@protonic.nl>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [ptxdist] Bug: Apparent unsolved circular dependency in HOST_SYSTEM_PYTHON3_SETUPTOOLS
Date: Wed, 18 Feb 2026 10:02:40 +0100 [thread overview]
Message-ID: <20260218100240.4aed79d9@erd003.prtnl> (raw)
Hi Michael,
While migrating a project to 2026.02.0 and building from scratch I came
across this build error:
----------------------------------------------
target: host-system-python3-setuptools.compile
----------------------------------------------
[...]
ImportError: Cannot import `packaging.licenses`.
Setuptools>=77.0.0 requires "packaging>=24.2" to work properly.
Please make sure you have a suitable version installed.
So apparently HOST_SYSTEM_PYTHON3_SETUPTOOLS is missing a dependency on
HOST_SYSTEM_PYTHON3_PACKAGING.
But adding this dependency and running oldconfig gets me this:
[..]host-system-python3-flit-core.in:3:error: recursive dependency detected!
[..]host-system-python3-flit-core.in:3: symbol HOST_SYSTEM_PYTHON3_FLIT_CORE is selected by HOST_SYSTEM_PYTHON3_PACKAGING
[..]host-system-python3-packaging.in:3: symbol HOST_SYSTEM_PYTHON3_PACKAGING is selected by HOST_SYSTEM_PYTHON3_SETUPTOOLS
[..]rules/host-system-python3-setuptools.in:3: symbol HOST_SYSTEM_PYTHON3_SETUPTOOLS is selected by HOST_SYSTEM_PYTHON3_FLIT_CORE
And indeed:
$ cat /usr/local/lib/ptxdist-2026.02.0/rules/host-system-python3-packaging.in
## SECTION=hosttools_noprompt
config HOST_SYSTEM_PYTHON3_PACKAGING
tristate
default y if ALLYES
select HOST_SYSTEM_PYTHON3
select HOST_SYSTEM_PYTHON3_FLIT_CORE
$ cat /usr/local/lib/ptxdist-2026.02.0/rules/host-system-python3-flit-core.in
## SECTION=hosttools_noprompt
config HOST_SYSTEM_PYTHON3_FLIT_CORE
tristate
default y if ALLYES
select HOST_SYSTEM_PYTHON3
select HOST_SYSTEM_PYTHON3_SETUPTOOLS
I solved this for my particular situation by removing "select
HOST_SYSTEM_PYTHON3_SETUPTOOLS" from host-system-python3-flit-core.in
I assume this will not work in every situation though. Not sure how to fix
this correctly and it is very possible that I am missing something here.
Best regards,
--
David Jander
reply other threads:[~2026-02-18 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260218100240.4aed79d9@erd003.prtnl \
--to=david@protonic.nl \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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