bug#33305: Guile's Autoconf macros play not well with make distcheck

bug#33305: Guile's Autoconf macros play not well with make distcheck

[Marc Nieper-Wißkirchen]

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

Consider an Autotools project that eventually wants to install some Guile
modules in the system. The canonical way to do this seems to add
GUILE_SITE_DIR to
https://www.gnu.org/software/guile/manual/html_node/Autoconf-Macros.html in
configure.ac and to use the variables GUILE_SITE and GUILE_SITE_CCACHE in
Makefile.am to determine the install targets.

However, this doesn't honor --prefix settings; in particular, make
distcheck fails for non-root users; see here for a general discussion:
https://www.gnu.org/software/automake/manual/html_node/Hard_002dCoded-Install-Paths.html

So in order to make use of GUILE_SITE and GUILE_SITE_CCACHE, I think we
need Autoconf macros in guile.m4 that allow to specify the prefix (as in
the Python example on the cited page).

-- Marc

P.S.: There is one more issue with guile.m4: When it finds the program
guile-2.2, it only searches for guild-2.2, but not for guild. However, at
least on Ubuntu systems, there is only guild, but no guild-2.2.

P.P.S.: Of course, in the long run we need integration of Guile in Autoconf
like Python and Elisp are already integrated.

[-- Attachment #2: Type: text/html, Size: 1534 bytes --]

bug#33305: Guile's Autoconf macros play not well with make distcheck

[David Pirotte]

[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]

Hello Mark,

	disclaimer: I'm not a Guile maintainer, just giving you my personal
	opinion here

> Consider an Autotools project that eventually wants to install some Guile
> modules in the system. The canonical way to do this seems to add
> GUILE_SITE_DIR to ...

> However, this doesn't honor --prefix settings; in particular, make
> distcheck fails for non-root users; see here for a general discussion:

The guile.m4 macros are not meant to (and shouldn't) honor variables such as
--prefix, that is the responsibility of the (autotool based) project author. The
guile.m4 macros and variables that it defines provide (and meant to only provide)
information about 'the Guile' that is 'visible' to your project (at configure and
make time ...).

There are solution though, here is an example of what I do [1].

> P.S.: There is one more issue with guile.m4: When it finds the program
> guile-2.2, it only searches for guild-2.2, but not for guild. However, at
> least on Ubuntu systems, there is only guild, but no guild-2.2.

That is expected, because 'guild' could point to 'another Guile' ... either it is an
Ubuntu problem, either guild was not properly post-fixed as requested, not sure, one
would have to check ...

HTH,
David

1]	http://git.savannah.nongnu.org/cgit/guile-lib.git/tree/

	[ see the configure.ac, Makefile.am and am/guile.mk ...
	[ I suggest you clone and try it (you'll need to run ./autogen.sh first)
	[ try with no option, then only using --prefix, then using both --prefix
	[ and --with-guile-site=yes 

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

bug#33305: Guile's Autoconf macros play not well with make distcheck

[David Pirotte]

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]


> ...
> There are solution though, here is an example of what I do [1].

Actually, I do this for all the projects maintain, and explain all this in detail on
the Guile-CV install page:

	https://www.gnu.org/software/guile-cv/install.html

	[ see "Install from ..." and following "Notes:" ...

David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]