unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: configuring apps for guile
Date: Sun, 16 Feb 2020 10:12:42 -0800	[thread overview]
Message-ID: <52bfb232-34a2-dfa6-8261-9309b97071f8@gmail.com> (raw)
In-Reply-To: <87tv3qza7c.fsf@gnu.org>

On 2/16/20 9:57 AM, Ludovic Courtès wrote:
> Hi,
>
> Matt Wette <matt.wette@gmail.com> skribis:
>
>> 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.
> I guess you would run:
>
>    ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
>
> in that case.
>
> Does that make sense?
>
> Ludo’.
Yes, but some naive person (like me, for example) would never guess
that is what is required.  (I ran into this installing bytestructures, 
IIRC).
And the info is in pkgconfig/guile-2.2.pc, but still requires chasing down
that resource.   Still thinking about it ...

Thanks, Ludo.

Matt




  reply	other threads:[~2020-02-16 18:12 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
2020-02-16 15:44       ` Matt Wette
2020-02-16 17:57     ` Ludovic Courtès
2020-02-16 18:12       ` Matt Wette [this message]
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=52bfb232-34a2-dfa6-8261-9309b97071f8@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).