Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>,
	Adam Duskett <adam.duskett@amarulasolutions.com>,
	James Hilliard <james.hilliard1@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v4 3/3] package/python3: bump version to 3.12.1
Date: Sat, 24 Feb 2024 14:58:23 +0100	[thread overview]
Message-ID: <87wmqut14w.fsf@48ers.dk> (raw)
In-Reply-To: <20240206233318.593730bd@windsurf> (Thomas Petazzoni via buildroot's message of "Tue, 6 Feb 2024 23:33:18 +0100")

>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

 > Hello Adam,
 > On Mon, 18 Dec 2023 15:04:56 -0700
 > Adam Duskett <adam.duskett@amarulasolutions.com> wrote:

 >> Python 3.12.1 has removed distutils support. As such, we remove the distutils
 >> option from pkg-python.mk as well.
 >> 
 >> Tested on Fedora 39, and Debian 11. All 68 package tests pass.
 >> 
 >> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
 >> ---
 >> v3 -> v4:
 >> - Drop distutils in pkg-python.mk
 >> - 3.12.0 -> 3.12.1

 > I applied, but after doing a number of changes. The most important one
 > is that I had to reintroduce some of our --disable options: for
 > ncurses, sqlite and expat. Indeed, without these, you ended up with the
 > Python code installed, but not the correspond native library (the
 > py_cv_module__<something>=n/a only disables building the native
 > library).

 > I split up the pkg-python.mk change into a separate commit, which is
 > made before the python 3.12 bump. Indeed, it's semantically separate.

 > Finally, I updated the Buildroot manual to no longer mention distutils
 > support. And I did a separate commit to update the Buildroot manual
 > with other _SETUP_TYPE values that we support.

We unfortunately are still having a number of build failures because of
this, E.G. for target == host or packages using the imp module and we
are very late for 2024.02.x, so I have reverted this again.

We can apply it again 2024.05.x after the release and work on the
remaining issues.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-02-24 13:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 22:04 [Buildroot] [PATCH v4 1/3] package/python-pygame: drop package Adam Duskett
2023-12-18 22:04 ` [Buildroot] [PATCH v4 2/3] package/python-crossbar: " Adam Duskett
2024-02-06 22:31   ` Thomas Petazzoni via buildroot
2023-12-18 22:04 ` [Buildroot] [PATCH v4 3/3] package/python3: bump version to 3.12.1 Adam Duskett
2023-12-24 22:12   ` Adam Duskett
2024-02-06 22:33   ` Thomas Petazzoni via buildroot
2024-02-07  2:32     ` James Hilliard
2024-02-24 13:58     ` Peter Korsgaard [this message]
     [not found]     ` <87wmqut14w.fsf__36507.8827760712$1708783134$gmane$org@48ers.dk>
2024-02-24 19:01       ` Bernd Kuhls
2024-02-25 11:21         ` Yann E. MORIN
2024-02-26 14:02           ` Arnout Vandecappelle via buildroot
2024-02-06 22:31 ` [Buildroot] [PATCH v4 1/3] package/python-pygame: drop package 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=87wmqut14w.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@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