From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Getting error 'kernel' must depend on 'host-system-python3' for 'python3'!
Date: Thu, 28 Mar 2024 11:52:17 +0000 [thread overview]
Message-ID: <2256e11b-9bd7-42a3-aeb9-cc82a52a04dc@mev.co.uk> (raw)
In-Reply-To: <b9b1078e-ca58-4477-8ad4-1ef354f474c8@mev.co.uk>
On 28/03/2024 11:36, Ian Abbott wrote:
> On 28/03/2024 10:59, Ian Abbott wrote:
>> On 28/03/2024 08:10, Michael Olbrich wrote:
>>> Put this in "platforms/kernel.fixup.in" in your BSP:
>>> ------------------------------->8----------------------------
>>> ## SECTION=base_kernel
>>>
>>> config KERNEL
>>> select HOST_SYSTEM_PYTHON3
>>>
>>> ------------------------------->8----------------------------
>>>
>>>> I'm currently using ptxdist 2024.03.0 but is also reproducible on the
>>>> ptxdist master branch.
>>>
>>> We should add that dependency Upstream as well. Something like
>>>
>>> config KERNEL_PYTHON3
>>> prompt "ensure Python3 is available"
>>> bool
>>> help
>>> Python3 is needed at build-time when CONFIG_DEBUG_INFO_BTF is
>>> enabled.
>>
>> Thanks. I combined the two and added the following to
>> "platforms/kernel.fixup.in" in my BSP:
>>
>> ------------------------------->8----------------------------
>> ## SECTION=base_kernel
>>
>> config KERNEL
>> select HOST_SYSTEM_PYTHON3 if KERNEL_PYTHON3
>>
>> config KERNEL_PYTHON3
>> prompt "ensure Python3 is available"
>> bool
>> select HOST_SYSTEM_PYTHON3
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> I realize that line is redundant. It was left over from my
> experimentation!
>
>> help
>> Python3 is needed at build-time when CONFIG_DEBUG_INFO is
^^^^^^^^^^^^^^^^^
And that should have been 'CONFIG_DEBUG_INFO_BTF' of course!
>> enabled
>> ------------------------------->8----------------------------
>
--
-=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company )=-
-=( registered in England & Wales. Regd. number: 02862268. )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-
next prev parent reply other threads:[~2024-03-28 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 17:17 Ian Abbott
2024-03-28 8:10 ` Michael Olbrich
2024-03-28 10:59 ` Ian Abbott
2024-03-28 11:36 ` Ian Abbott
2024-03-28 11:52 ` Ian Abbott [this message]
2024-03-28 15:04 ` Michael Olbrich
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=2256e11b-9bd7-42a3-aeb9-cc82a52a04dc@mev.co.uk \
--to=abbotti@mev.co.uk \
--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