From: "Ludovic Courtès" <ludo@gnu.org>
To: divoplade <d@divoplade.fr>
Cc: help-guix@gnu.org
Subject: Re: How do I set LTDL_LIBRARY_PATH?
Date: Tue, 29 Sep 2020 16:02:38 +0200 [thread overview]
Message-ID: <87zh5865q9.fsf@gnu.org> (raw)
In-Reply-To: <5e8245d2af36f13d6119b53cd14c2ebd7ca8fdf8.camel@divoplade.fr> (divoplade's message of "Thu, 17 Sep 2020 22:58:36 +0200")
Hi,
divoplade <d@divoplade.fr> skribis:
> I have written a small C guile module to access (some parts of) the GNU
> nettle library. I can install it with guix, but then if I try to load
> it from within an environment:
>
> guix environment --ad-hoc guile guile-nettle -- guile <<EOF
> (load-extension "libguile-nettle" "init_nettle")
> EOF
>
> guile does not find "libguile-nettle" (In procedure dynamic-link: file:
> "libguile-nettle", message: "file not found")
>
> This is because guile expects it to be in LTDL_LIBRARY_PATH, and guix
> does not set that up.
Common practice is to arrange so that bindings refer to C libraries by
absolute file name. For example:
--8<---------------cut here---------------start------------->8---
$ grep /libgcrypt $(find $(guix build guile-gcrypt) -name \*config.scm)
"/gnu/store/qc3k3kd458pgrqsc7ih641160q81npwq-libgcrypt-1.8.5/lib/libgcrypt")
$ grep /libz $(find $(guix build guile-zlib) -name \*config.scm)
"/gnu/store/rykm237xkmq7rl1p0nwass01p090p88x-zlib-1.2.11/lib/libz")
--8<---------------cut here---------------end--------------->8---
HTH!
Ludo’.
prev parent reply other threads:[~2020-09-29 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 20:58 How do I set LTDL_LIBRARY_PATH? divoplade
2020-09-29 14:02 ` Ludovic Courtès [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh5865q9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=d@divoplade.fr \
--cc=help-guix@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).