From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Guile extensions path (includes PATCH)
Date: Mon, 29 Jun 2020 19:54:35 -0700 [thread overview]
Message-ID: <CA+XASoXaztbs25yH_kkZmKC2-+eKYaiv-qkqP07+2kp56+MC8Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 962 bytes --]
Hi,
I was adding guile-ncurses to homebrew-guile and realized there might be an
issue in the documentation.
According to this:
https://www.gnu.org/software/guile/manual/html_node/Modules-and-Extensions.html
the extensions directory is /usr/lib/guile/3.0/ (or
/usr/local/lib/guile/3.0/m depending on your libdir). This is the directory
where guile-ncurses installs libguile-ncurses library.
However, I then saw that guile-readline was installed in
/usr/local/lib/guile/3.0/extensions. I initially thought this was a
Homebrew specific location. I looked at the Formula but there's nothing
specific to Homebrew there.
Then, I looked at guile and found this:
http://git.savannah.gnu.org/cgit/guile.git/tree/libguile/Makefile.am#n772
which indicates the extensions path is really /usr/lib/guile/3.0/extensions.
I patched guile-ncurses with this and it works fine now on macOS.
In case this is correct, I'm including a patch to fix the manual.
Best,
Aleix
[-- Attachment #1.2: Type: text/html, Size: 3546 bytes --]
[-- Attachment #2: 0001-doc-update-guile-extensions-path.patch --]
[-- Type: application/octet-stream, Size: 1139 bytes --]
From 4c0ecac85bb3c1af9b66f00963d34e96096c3889 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Aleix=20Conchillo=20Flaqu=C3=A9?= <aconchillo@gmail.com>
Date: Mon, 29 Jun 2020 19:51:30 -0700
Subject: [PATCH] doc: update guile extensions path
* doc/ref/api-foreign.texi: append "extensions" to extensiondir.
---
doc/ref/api-foreign.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-foreign.texi b/doc/ref/api-foreign.texi
index b0d6c249b..b0306fadf 100644
--- a/doc/ref/api-foreign.texi
+++ b/doc/ref/api-foreign.texi
@@ -373,7 +373,7 @@ When loaded with @code{(use-modules (foo bar))}, the
object file in Guile's @code{extensiondir}, which is usually a
subdirectory of the @code{libdir}. For example, if your libdir is
@file{/usr/lib}, the @code{extensiondir} for the Guile @value{EFFECTIVE-VERSION}.@var{x}
-series will be @file{/usr/lib/guile/@value{EFFECTIVE-VERSION}/}.
+series will be @file{/usr/lib/guile/@value{EFFECTIVE-VERSION}/extensions}.
The extension path includes the major and minor version of Guile (the
``effective version''), because Guile guarantees compatibility within a
--
2.27.0
reply other threads:[~2020-06-30 2:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CA+XASoXaztbs25yH_kkZmKC2-+eKYaiv-qkqP07+2kp56+MC8Q@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).