From: "Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>
To: 33305@debbugs.gnu.org
Subject: bug#33305: Guile's Autoconf macros play not well with make distcheck
Date: Wed, 7 Nov 2018 17:07:24 +0100 [thread overview]
Message-ID: <CAEYrNrS_CPHHMBJSLtKVME1SqfaYXk0=BHR=ZsfdGu60wcSQ6g@mail.gmail.com> (raw)
[-- 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 --]
next reply other threads:[~2018-11-07 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 16:07 Marc Nieper-Wißkirchen [this message]
2018-11-10 20:20 ` bug#33305: Guile's Autoconf macros play not well with make distcheck David Pirotte
2018-11-10 21:24 ` David Pirotte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEYrNrS_CPHHMBJSLtKVME1SqfaYXk0=BHR=ZsfdGu60wcSQ6g@mail.gmail.com' \
--to=marc@nieper-wisskirchen.de \
--cc=33305@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).