After emerging guile-2.2.7-r102 generates an env dropin that sets PKG_CONFIG_PATH outside of the prefix directory, instead of the location within the prefix. This results in failures with guile-single.class being unable to fix the pkgconfig files. Reproducible: Always Actual Results: $ cat /home/terin/gentoo/etc/env.d/50guile97997 PKG_CONFIG_PATH="/usr/share/guile-data/2.2/pkgconfig" INFOPATH="/home/terin/gentoo/usr/share/guile-data/2.2/info" During an emerge I get an error: * Could not get guile out of guile-2.2. Did you source /etc/profile after an update? * * Call stack: * ebuild.sh, line 136: Called pkg_setup * ebuild.sh, line 374: Called guile-single_pkg_setup * guile-single.eclass, line 218: Called guile_export 'GUILE' 'GUILD' 'GUILESNARF' * guile-utils.eclass, line 218: Called _guile_pcvar 'guile' * guile-utils.eclass, line 213: Called die * The specific snippet of code: * $(tc-getPKG_CONFIG) --variable="$1" guile-"${gver}" \ * || die "Could not get $1 out of guile-${gver}. ${tip}" Setting PKG_CONFIG_PATH to the correct location in the prefix results in working ebuilds.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4f485d53ab5b0b499d4e13aefe053cd38b4ac500 commit 4f485d53ab5b0b499d4e13aefe053cd38b4ac500 Author: Arsen Arsenović <arsen@gentoo.org> AuthorDate: 2025-02-24 00:37:01 +0000 Commit: Arsen Arsenović <arsen@gentoo.org> CommitDate: 2025-02-27 23:13:51 +0000 dev-scheme/guile: fix pcdir path inside env.d file Closes: https://bugs.gentoo.org/943022 Signed-off-by: Arsen Arsenović <arsen@gentoo.org> dev-scheme/guile/guile-2.2.7-r103.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
