Created attachment 922561 [details] build fail log Configuring testCommandLine.sh.test using configuration Configuring testCommandLineModules.sh.test using configuration Configuring testWarnings.sh.test using configuration Dependency gio-2.0 found: YES 2.84.0 (cached) Program /usr/bin/glib-compile-resources found: YES (/usr/bin/glib-compile-resources) installed-tests/js/meson.build:43:23: ERROR: Include dir /usr/share/gobject-introspection-1.0/tests does not exist. emerge -vp =gnome-extra/cjs-6.4.0 [ebuild R ] gnome-extra/cjs-6.4.0::gentoo USE="cairo readline sysprof -examples -test" 0 KiB
Created attachment 922562 [details] emerge info
Why aren't they just using subdir_done() if -Dinstalled_tests=disabled?
It still generates test() entries either way. The installed-tests build option simply controls whether the src_test tests are additionally installed in src_install.
gobject-introspection-1.82 adds a test option which also drops installing tests, so that explains it.
(In reply to Sam James from comment #4) > gobject-introspection-1.82 adds a test option which also drops installing > tests, so that explains it. .. 1.84
Created attachment 923276 [details] cjs-6.4.0 build log
Created attachment 923277 [details] gjs-1.80.2 build log
It's worth noting that dev-libs/gjs (of which cjs is a fork) has the exact same issue. While fixing gjs/cjs is undoubtedly the correct solution, would the most expedient fix be for gobject-introspection to continue installing those files for the time being?
(In reply to Matthew Turnbull from comment #8) > It's worth noting that dev-libs/gjs (of which cjs is a fork) has the exact > same issue. > > While fixing gjs/cjs is undoubtedly the correct solution, would the most > expedient fix be for gobject-introspection to continue installing those > files for the time being? Just forcing +test IUSE on dev-libs/gobject-introspection makes cjs be able to compile. While this is not a solution but just a workaround and is quick and harmless, can it be set "for now" while a proper fix is found?
I'd prefer to not add a workaround in gobject-introspection until there's an upstream report for cjs/gjs we can refer to.
https://gitlab.gnome.org/GNOME/gjs/-/commit/65b5fa5d0d1dda17301e8ac751f32dc46a575e52
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c7e8d07963bd013c2615d4a88ef2f781187cab68 commit c7e8d07963bd013c2615d4a88ef2f781187cab68 Author: Sam James <sam@gentoo.org> AuthorDate: 2025-04-07 03:45:21 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-04-07 03:46:18 +0000 dev-libs/gobject-introspection: install tests unconditionally for now Enable building the tests (and installing them) unconditionally for now as a workaround for old gnome-extra/cjs and dev-libs/gjs, see bug #952011. Besides, it isn't ideal even before this, given USE=test shouldn't control installation of tests at all (rather USE=test-install). Bug: https://bugs.gentoo.org/952011 Signed-off-by: Sam James <sam@gentoo.org> ...pection-1.84.0.ebuild => gobject-introspection-1.84.0-r1.ebuild} | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
