From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
Evan Straw <evan.straw99@gmail.com>
Cc: 39079@debbugs.gnu.org
Subject: bug#39079: SBCL CFFI from Guix unable to find dynamic libraries
Date: Tue, 14 Jan 2020 11:25:39 +0100 [thread overview]
Message-ID: <87d0bmpc64.fsf@ambrevar.xyz> (raw)
In-Reply-To: <m136cie49w.fsf@ordinateur-de-catherine--konrad.home>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> Not with shared libraries in Guix, I agree. But the problem was with
> shared libraries from the foreign distros. Guix actually tries hard
> *not* to make them accessible (in order to ensure reproducibility),
> so I wonder if this bug should be closed as "not a bug".
The snippet I shared above allows the user to set SBCL to libraries from
the given locations.
I can't see why this wouldn't work on a foreign distribution. But let's
wait until Evan shares his complete setup.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-14 10:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 3:38 bug#39079: SBCL CFFI from Guix unable to find dynamic libraries Evan Straw
2020-01-11 9:58 ` Pierre Neidhardt
2020-01-13 22:11 ` Evan Straw
2020-01-13 22:22 ` Pierre Neidhardt
2020-01-14 5:52 ` Konrad Hinsen
2020-01-14 9:38 ` Pierre Neidhardt
2020-01-14 10:11 ` Konrad Hinsen
2020-01-14 10:25 ` Pierre Neidhardt [this message]
2020-01-14 21:30 ` Evan Straw
2020-01-15 7:45 ` Pierre Neidhardt
2020-01-15 8:53 ` Konrad Hinsen
2020-01-15 9:13 ` Pierre Neidhardt
2020-01-16 18:36 ` Evan Straw
2020-01-17 15:49 ` Pierre Neidhardt
2020-01-17 21:24 ` Ludovic Courtès
2020-01-17 21:27 ` Ludovic Courtès
2020-01-18 10:50 ` Pierre Neidhardt
2020-01-18 16:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0bmpc64.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=39079@debbugs.gnu.org \
--cc=evan.straw99@gmail.com \
--cc=konrad.hinsen@fastmail.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.