I would suggest not trying to figure out PACKAGECONFIGs just yet, but
rather go to the source of the error: inspect ${T}/log.do_configure
and ${T}/run.do_configure. Are options to enable/disable python passed
in? If yes, then something in PACKAGECONFIG settings doesn't quite
work. If no, then libxml somehow needs python at build time even
without those options, and this should be looked at separately by
checking in libxml source code what the failing check for python
actually does, and is it guarded by any options.


Alex

On Mon, 22 Jan 2024 at 14:40, Quentin Schulz via
lists.yoctoproject.org
<quentin.schulz=theobroma-systems....@lists.yoctoproject.org> wrote:
>
> Hi Holger,
>
> On 1/22/24 14:33, Sebert, Holger.ext via lists.yoctoproject.org wrote:
> > [You don't often get email from 
> > holger.sebert.ext=karlstorz....@lists.yoctoproject.org. Learn why this is 
> > important at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > Hi Richard,
> >
> > Von: Richard Purdie <richard.pur...@linuxfoundation.org>
> >> Try:
> >>
> >> PACKAGECONFIG:remove:class-target:pn-libxml2 = "python"
> >>
> >
> > Tried it, but same error appears (“Python not found” in libxml2-native).
> >
>
> What does
> bitbake-getvar -r libxml2-native PACKAGECONFIG
> and
> bitbake-getvar -r libxml2 PACKAGECONFIG
>
> return?
>
> I'm not entirely sure if the former will work since bitbake-getvar
> expects a recipe and libxml2 isn't reaaaaally a recipe on its own.
>
> If the former doesn't work, we need to check for
> PACKAGECONFIG:class-native and PACKAGECONFIG:class-target in
> bitbake-getvar -r libxml2 PACKAGECONFIG to debug this further.
>
> Cheers,
> Quentin
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62221): https://lists.yoctoproject.org/g/yocto/message/62221
Mute This Topic: https://lists.yoctoproject.org/mt/103871920/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to