From: Peter Korsgaard <peter@korsgaard.com>
To: Julien Olivain <ju.o@free.fr>
Cc: "Vincent Stehlé" <vincent.stehle@arm.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] boot/grub2: needs host-python3
Date: Thu, 03 Oct 2024 13:05:47 +0200 [thread overview]
Message-ID: <874j5to390.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87frpiiy6k.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Sun, 29 Sep 2024 11:52:51 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Julien" == Julien Olivain <ju.o@free.fr> writes:
> Hi,
>>> Given that it apparently doesn't need any special python modules
>>> could
>>> we use $(BR2_PYTHON3_HOST_DEPENDENCY) instead to only build python3 if
>>> not available on the host / older than 3.4?
>> Yes, I confirm that for now, there is no specific python module
>> requirement, and Python 3.4 should also be sufficient. So we could
>> switch to BR2_PYTHON3_HOST_DEPENDENCY to save the time of the host
>> python build.
>> The same comment applies to the Linux kernel.
>> Since those patches were recently merged in [1] and [2], I'll propose
>> followup patches as an improvement.
> Great, thanks!
Committed to 2024.02.x and 2024.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-03 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 17:19 [Buildroot] [PATCH 1/1] boot/grub2: needs host-python3 Julien Olivain
2024-09-14 14:37 ` Yann E. MORIN
2024-09-21 8:18 ` Peter Korsgaard
2024-09-29 9:24 ` Julien Olivain
2024-09-29 9:52 ` Peter Korsgaard
2024-10-03 11:05 ` Peter Korsgaard [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=874j5to390.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=vincent.stehle@arm.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