odd ninja-build behavior - current
by bw42 from LinuxQuestions.org on (#5DXMW)
Ran into an odd issue with Ninja during my powerpc64le build of -current.
It started throwing Failed: messages and constantly failing the builds.
Running ninja in the build folders manually, repeatedly, would finish the build and then the .SlackBuild can run and build the package like normal.
Running ninja with -d explain shows a lot of messages saying files were missing or dirty.
Tried downgrading ninja and meson, tried dev versions from git masters, all the same issue.
On a whim I tried using cmake to build ninja instead of the python bootstrap, errors went away.
If someone better at python has some thoughts on what I can check out for why the standard method is causing it, would be appreciated.
It started throwing Failed: messages and constantly failing the builds.
Running ninja in the build folders manually, repeatedly, would finish the build and then the .SlackBuild can run and build the package like normal.
Running ninja with -d explain shows a lot of messages saying files were missing or dirty.
Tried downgrading ninja and meson, tried dev versions from git masters, all the same issue.
On a whim I tried using cmake to build ninja instead of the python bootstrap, errors went away.
If someone better at python has some thoughts on what I can check out for why the standard method is causing it, would be appreciated.