On Fri Oct 25, 2024 at 5:13 PM CEST, Santiago Vila wrote:
What I see is that the top level meson.build has subdir('doc') and
doc/meson.build has a reference to meson-docs, which apparently is
setup in a way that meson-docs may be either present or missing.
The error happens when genrefman.py is invoked in meson-docs:
/<<PKGBUILDDIR>>/build/muon internal exe -e
/<<PKGBUILDDIR>>/build/.muon/custom_tgt_env/meson_reference_33_dat --
../subprojects/meson-docs/docs/genrefman.py -q -l fastyaml -g man -o
subprojects/meson-docs/meson-reference.3 --no-modules
/bin/sh: 1: /<<PKGBUILDDIR>>/build/muon: Permission denied
I believe this is just a misleading log message due to the parallel
execution of build targets. I suspect the genrefman target is invoked at
the same time as the linking step which overwrites build/muon, and fails
to run since build/muon is currently being written to. Try to replace
"$dir/muon" with "$dir/muon-bootstrap", as suggested by Vincent Torri;
I believe it should fix the issue (of course the build/muon invocations
in dh_auto_build need to be changed too).
Seems a missing dependency to me. Where is stated in
meson-docs/meson.build that muon should exist before trying to use it?
muon is the thing executing the build itself, you aren't supposed to
explicitly say that muon needs to exist in order to run a muon build. It
would be like checking that make exists in a makefile :)
Bye!
