On Mon, 2023-01-16 at 19:21 +0000, Jose Quaresma wrote: > Hi Richard, > > I am seeing some build errors like this at the end of the build whre bibake > segment fault. > My problem is this happens on a build that doesn't use uninative, > does bitbake require uninative to build on master?
No, it doesn't. My worry was that uninative didn't contain libgcc which meant that builds could fail like this if it wasn't present. The reason for the change is threading in bitbake itself and the thread.join() calls which seem to trigger pthread_cancel() calls under some circumstances. Having libgcc present in uninative seemed like a good idea so I've ensured that. I wasn't entirely convinced it would solve it, I half expected to see a new/different error replacing it. Is libgcc present on your build system? It would seem strange for it not to be but that is what the error message suggests. I've also seem mention of issues with this in some versions of python but I've not seen any errors on the autobuilder since I ensured it was present in uninative. > This is my build log where bitbake crash at the end: > > INFO: Build completion summary: > INFO: do_populate_sysroot: 100.0% sstate reuse(387 setscene, 0 scratch) > INFO: do_deploy_source_date_epoch: 100.0% sstate reuse(5 setscene, 0 > scratch) > INFO: do_deploy_archives: 100.0% sstate reuse(400 setscene, 0 scratch) > INFO: do_create_spdx: 100.0% sstate reuse(364 setscene, 0 scratch) > INFO: do_create_runtime_spdx: 100.0% sstate reuse(342 setscene, 0 scratch) > INFO: do_package_qa: 100.0% sstate reuse(243 setscene, 0 scratch) > INFO: do_package: 100.0% sstate reuse(26 setscene, 0 scratch) > INFO: do_packagedata: 100.0% sstate reuse(243 setscene, 0 scratch) > INFO: do_package_write_ipk: 100.0% sstate reuse(243 setscene, 0 scratch) > INFO: do_populate_lic: 100.0% sstate reuse(395 setscene, 0 scratch) > INFO: Writing buildhistory > INFO: Writing buildhistory took: 10 seconds > libgcc_s.so.1 must be installed for pthread_cancel to work > /lmp/bb-build.sh: line 24: 91770 Aborted (core dumped) > bitbake -D ... This is the build system's python saying it can't find libgcc_s.so.1 so I'd start by checking it is there. I'm assuming you're not using buildtools? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#176015): https://lists.openembedded.org/g/openembedded-core/message/176015 Mute This Topic: https://lists.openembedded.org/mt/96152280/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
