El 25/10/24 a las 16:33, Andrea Pappacoda escribió:
override_dh_auto_build:
---> ln -s ../meson-docs subprojects/
CC="$(CC_FOR_BUILD)" CFLAGS="$(CPPFLAGS_FOR_BUILD) $(CFLAGS_FOR_BUILD)"
LDFLAGS="$(LDFLAGS_FOR_BUILD)" ./bootstrap.sh build
build/muon setup -Dprefix=/usr -Dsamurai=disabled -Dreadline=bestline
build
ninja -C build --verbose
How does this create issues? Upstream's build system already downloads the
meson-docs wrap into the subprojects directory on demand. Here I'm downloading
the meson-docs component ahead of time via uscan's multiple upstream tarballs
support instead of letting muon download it from the internet at build time,
but I really can't think of how this can create issues.
When you download a meson/muon wrap, it gets stored in the subprojects
directory and is not deleted, so if having stuff in subprojects/ breaks muon's
build this is definitely a muon bug.
Please note that I don't really know this package or the ninja build system
well enough to tell.
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
Seems a missing dependency to me. Where is stated in meson-docs/meson.build
that muon should exist
before trying to use it?
Thanks.
