Guile executables won't be found by the configure script
In a project freshly created with Hall, the configure script won't find the Guile pieces
This an excerpt of the configure output
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.3 checking for guild-2.2... no checking for guile-config-2.2... no checking for guile-tools-2.2... no checking for Guile site directory... /usr/share/guile/site/2.2 checking for Guile site-ccache directory using pkgconfig... /usr/lib/x86_64-linux-gnu/guile/2.2/site-ccache checking for Guile extensions directory... /usr/lib/x86_64-linux-gnu/guile/2.2/extensions configure: error: 'guild' binary not found; please check your guile-2.x installation.
This happens on Ubuntu 18.04.1 and the Guile 2.2.3 provided by the system
What happens is that the Guile found has the "-2.2" suffix
Consequently, all the guile tools are expected to have the same suffix
And because they haven't got the same suffix, they won't be found.
The solution is to point configure to Guile like this:
In this case, all the tools searched won't be expected to have the "-2.2" suffix and all goes well.
With other Guile projects Guile gets correctly identified with no hints by the user.
I think this has something to do with the version of the included
guile.am file but I don't now enough in order to diagnose.