From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: Guile extensions path (includes PATCH)
Date: Wed, 29 Jul 2020 11:07:11 -0700 [thread overview]
Message-ID: <CA+XASoVBJ5AG3aN5Wv4yJf3OnUxv_UY49TP=xNE69r3eLYEfuQ@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoXaztbs25yH_kkZmKC2-+eKYaiv-qkqP07+2kp56+MC8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Any thoughts on this one?
Thanks,
Aleix
On Mon, Jun 29, 2020 at 7:54 PM Aleix Conchillo Flaqué <aconchillo@gmail.com>
wrote:
> 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 #2: Type: text/html, Size: 4392 bytes --]
prev parent reply other threads:[~2020-07-29 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 2:54 Guile extensions path (includes PATCH) Aleix Conchillo Flaqué
2020-07-29 18:07 ` Aleix Conchillo Flaqué [this message]
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+XASoVBJ5AG3aN5Wv4yJf3OnUxv_UY49TP=xNE69r3eLYEfuQ@mail.gmail.com' \
--to=aconchillo@gmail.com \
--cc=guile-devel@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).