From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15943] Reevaluate Python3 patches
Date: Mon, 29 Apr 2024 01:08:28 +0000 [thread overview]
Message-ID: <bug-15943-163-rp6LwvKpsf@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15943-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15943
--- Comment #1 from Vincent Fazio <vfazio@xes-inc.com> ---
The original patch list was based on master with python 3.12 patches which got
reverted so it's not completely accurate based on current master.
I submitted http://lists.busybox.net/pipermail/buildroot/2024-April/689926.html
to address a few patches to reduce the work needed for the python 3.12.3 bump
The plan for python 3.12 should be to drop uclibc support completely as
upstream has disabled it explicitly in 3.13. This allows us to drop a couple
of additional patches but will come at the cost of some platforms no longer
having cpython available (if uclibc is their only available libc).
patch 0016-configure.ac-fixup-CC-print-multiarch-output-for-mus.patch should be
dropped in favor of a new patch that swaps $build_os with $host_os without the
need for additional handling for uclibc
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-29 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 15:30 [Buildroot] [Bug 15943] New: Reevaluate Python3 patches bugzilla
2024-04-29 1:08 ` bugzilla [this message]
2024-06-15 15:24 ` [Buildroot] [Bug 15943] " bugzilla
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=bug-15943-163-rp6LwvKpsf@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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