Hi Ross, Here is the background of this: Initially we found this issue, when we are trying to build the Arm FVP for openbmc, as you can see from the discussion here: https://gerrit.openbmc.org/c/openbmc/openbmc/+/70070/comment/4a963c24_75b11840/ So thanks to the kind help from Patrick Williams (cc'ed here), he proposed to try this fix: > diff --git a/poky/meta/recipes-kernel/perf/perf.bb > b/poky/meta/recipes-kernel/perf/perf.bb > index 11fa917649..d39265367b 100644 > --- a/poky/meta/recipes-kernel/perf/perf.bb > +++ b/poky/meta/recipes-kernel/perf/perf.bb > @@ -54,7 +54,7 @@ PROVIDES = "virtual/perf" > inherit linux-kernel-base kernel-arch manpages # needed for building the tools/perf Python bindings > -inherit_defer ${@bb.utils.contains('PACKAGECONFIG', 'python', > 'python3targetconfig', '', d)} > +inherit_defer ${@bb.utils.contains('PACKAGECONFIG', 'python', > 'setuptools3-base python3targetconfig', '', d)} However, it is still not working. I added a workaround with this patch: https://gerrit.openbmc.org/c/openbmc/openbmc/+/71017 Still, Patrick thinks that this should not be the case, and the proper fix should be done via OpenEmbedded. Currently we are not sure how to fix this properly and don't have any idea. Much appreciated if you or anyone have any idea on this! Thank you, Sheng On Thu, 25 Apr 2024 at 18:45, Lean Sheng Tan via lists.openembedded.org wrote: > Hi Ross, > Thank you for your quick response! > That makes sense now. > > Regarding your statement: > "That dependency in btrfs-tools might be actually not required, or you > might want to make the recipe depend on python3-native." > May I know if something has to be fixed from the meta-openembedded or > generic yocto build? > If not, what would be the best way to approach it? > > Thanks again. > > Best Regards, > Sheng > > > On Thu, 25 Apr 2024 at 18:34, Ross Burton wrote: > >> On 25 Apr 2024, at 13:29, Sheng Lean Tan via lists.openembedded.org >> wrote: >> > >> > Hi, >> > Good day to openembedded community! >> > >> > This is my first post - hope this is the right place to ask for help >> regarding a build issue, as refer from here: >> > >> https://gerrit.openbmc.org/c/openbmc/openbmc/+/71017/comment/195b742f_6cf8da09/ >> > >> > Currently, we saw this issue when building this on openBMC which is >> based on Yocto:- >> > The error found when manually run bitbake btrfs-tools-native is as >> follows: >> > checking for a Python interpreter with version >= 3.4... python3 >> > checking for python3... >> /home/apwillia/local/builds/lf-build-yosemite4/tmp/hosttools/python3 >> > checking for python3 version... 3.11 >> > checking for python3 platform... linux >> > checking for GNU default python3 prefix... ${prefix} >> > checking for GNU default python3 exec_prefix... ${exec_prefix} >> > checking for python3 script directory (pythondir)... >> ${libdir}/python3.11/site-packages >> > checking for python3 extension module directory (pyexecdir)... >> ${libdir}/python3.11/site-packages >> > checking for python-3.11... no >> > configure: error: Package requirements (python-3.11) were not met: >> > >> > No package 'python-3.11' found >> > >> > To bypass this, we have to manually remove in OpenBMC with this tweak: >> > PACKAGECONFIG:remove:pn-btrfs-tools-native = "python" >> > >> > May I know if this is a real bug, or if we did miss something from our >> configuration? >> >> It looks like the native btrfs-tools is trying to build against the host >> python: >> >> > checking for python3... >> /home/apwillia/local/builds/lf-build-yosemite4/tmp/hosttools/python3 >> >> So the problem is that your build host doesn’t have python3-dev or >> similar installed. >> >> That dependency in btrfs-tools might be actually not required, or you >> might want to make the recipe depend on python3-native. >> >> Ross > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#198706): > https://lists.openembedded.org/g/openembedded-core/message/198706 > Mute This Topic: https://lists.openembedded.org/mt/105729019/6757431 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ > sheng.tan@9elements.com] > -=-=-=-=-=-=-=-=-=-=-=- > >