On Thu, 9 Mar 2023 at 11:39, Richard Purdie <[email protected]> wrote:
> Before we start changing core dependencies, we need to better > understand what happened there. Whilst this patch might fix this case, > we'd likely just leave races elsewhere as other tasks call git too. > > Which recipe was this? > Why is git calling into python? > Why didn't the staging code to move libs into position before binaries > prevent this? The recipe was libslirp-native (I don't think it matters). Git itself is not calling into python; it's poky/scripts/git, which is a python wrapper script around git. I don't have a definite answer to the last question - I believe the staging code also removes 'outdated' sysroot items before installing current ones, and that's where the window of having python binary, but not its library may have occurred? Still, there seems to be a general problem here: prepare_recipe_sysroot runs at the same time as tasks (such as unpack) that have PATH pointing to directories being modified by it. So there's no determinism in which python (native one or one from the host) is going to be used for example; it may randomly change midway through the task. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#178220): https://lists.openembedded.org/g/openembedded-core/message/178220 Mute This Topic: https://lists.openembedded.org/mt/97493237/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
