Package: guile-2.2 Version: 2.2.4+1-1 Severity: normal Building gwave against guile-2.2 fails if gwave runs dh_autoreconf, that is bexause the autoreconf'ed configure script fails to find guild and guile-config/tools binaries, relevant configure log below:
configure: checking for guile 2.2
configure: found guile 2.2
checking for guile-2.2... /usr/bin/guile-2.2
checking for Guile version >= 2.2... 2.2.4
checking for guild-2.2... no
checking for guile-config-2.2... no
checking for guile-tools-2.2... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for GUILE... yes
configure: error: 'guild' binary not found; please check your guile-2.x
installation.
The problem is because after autoreconf, the configure script searches
for guild with the -2.2 suffix, yet the guile-2.2-dev package installs
guild without that suffix, although guile binary has the -2.2 suffix in
guile-2.2 package. Yet in /usr/share/aclocal/guile.m4 it says:
# @code{guile} is still not found, signal an error. The suffix, if any,
# that was required to find @code{guile} will be used for @code{guild}
# as well.
Hence,I beleive that that there is an issue with guile-2.2 package.
Either the guild & guile-config/tools binaries shpuld be insyalled with
-2.2 suffix (probably installing symlinks with no suffix to the
respective -2.2 suffixed binaries), or the guile.m4 script needs to be
fixed.
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761
8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
signature.asc
Description: PGP signature
