From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: configuring apps for guile
Date: Sun, 16 Feb 2020 07:43:09 -0800 [thread overview]
Message-ID: <57dbd09b-eb8c-eada-e06a-404f16ea1ea7@gmail.com> (raw)
In-Reply-To: <b72887eb-ec1e-b235-a46a-441ec70c928a@gmail.com>
On 2/16/20 7:28 AM, Matt Wette wrote:
> On 2/16/20 6:48 AM, Ludovic Courtès wrote:
>>
>> moddir = $(datadir)/guile/site/$(GUILE_EFFECTIVE_VERSION)
>> godir = $(libdir)/guile/$(GUILE_EFFECTIVE_VERSION)/site-ccache
>>
> What if you have a system that gives this (e.g., Ubuntu 18.04):
>
> mwette$ /usr/bin/guile -c "(display (assq-ref %guile-build-info
> 'prefix)) (newline)"
> /usr
>
> mwette$ /usr/bin/guile -c "(display (%site-ccache-dir)) (newline)"
> /usr/lib/x86_64-linux-gnu/guile/2.2/site-ccache
>
> I'm not sure that guile will find .go files installed in
> /usr/lib/guile/2.2/site-ccache.
>
>
And for me, things get more bizarre. If I have another guile installed
in my path
under /opt/local I get
mwette$ /usr/bin/guile -c "(display (%site-ccache-dir)) (newline)"
/opt/local/lib/guile/2.2/site-ccache
I have no clue how that is happening. I assume these paths are hardcoded.
Just to be sure:
mwette$ env | grep GUILE
GUILE_WARN_DEPRECATED=detailed
GUILE_LOAD_PATH=/home/mwette/opt/guile
next prev parent reply other threads:[~2020-02-16 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 13:54 configuring apps for guile Matt Wette
2020-02-12 14:04 ` Matt Wette
2020-02-13 6:59 ` Jeremy Korwin-Zmijowski
2020-02-13 21:59 ` Jan Wedekind
2020-02-16 14:48 ` Ludovic Courtès
2020-02-16 15:28 ` Matt Wette
2020-02-16 15:43 ` Matt Wette [this message]
2020-02-16 15:44 ` Matt Wette
2020-02-16 17:57 ` Ludovic Courtès
2020-02-16 18:12 ` Matt Wette
2020-02-17 9:21 ` Ludovic Courtès
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=57dbd09b-eb8c-eada-e06a-404f16ea1ea7@gmail.com \
--to=matt.wette@gmail.com \
--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).