On Fri, 14 Jun 2024 at 07:15, Mayank Pandey via Lists.Yoctoproject.Org <pandeymayank96=gmail....@lists.yoctoproject.org> wrote: > Thanks for the input. The thing is, the issue is not coming in the plain poky > build, that I had tried already. In the custom build that we have, the issue > is coming. We don't get this in kirkstone (4.0) but beyond that we are > getting the problem with the upgrades. Any pointers as to where we should > look at to fix this? I read a suggestion on a forum that we can disable > Wimplicit-function-declaration for this specific case, but that is pretty > much a hack and won't be building the curses module with Python. > Any other suggestions on where to look for?
You need to narrow down the difference between working build and broken build. Start with the working build: inspect the build directory of python3 and find out where setupterm() is declated, and how that declaration is picked up by the compiler when it builds _cursesmodule.c. Or maybe _cursesmodule.c isn't built at all? Then look at the broken build and find out what is happening there. Is there a difference in how the compiler is invoked (log.do_compile)? Are the includes conditional and the condition for the needed one is false? Or curses is enabled in the broken build and disabled in the working one? Investigating build failures like this are a necessary skill with Yocto, you have to develop it. Formulate a set of questions, then answer them in order, eliminating possibilities. Or hire a consultant. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63348): https://lists.yoctoproject.org/g/yocto/message/63348 Mute This Topic: https://lists.yoctoproject.org/mt/106648183/21656 Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
