From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>,
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 06:52:06 +0100 [thread overview]
Message-ID: <c2f7cc71-d672-e2f8-6280-664d26e680e1@fastmail.net> (raw)
In-Reply-To: <87o8v7yp23.fsf@ambrevar.xyz>
Hi Pierre and Evan,
> This seems to be a red herring, as Guix does not change how CFFI loa > libraries. The only thing that changes is where the libraries are
found> with Guix packages.
I don't know about the details of SBCL and its CFFI, but there is a
difference in how Guix handles shared libraries that I discovered
recently and which might be related.
Programs compiled under Guix don't use the search path feature for
shared libraries (via Guix' own copy of ldd.so). All references to
shared libraries use the full path to the store. So if you compile sbcl
under Guix, it will never look for libraries that are referenced by name
only (without the full path). The foreign distro probably relies on that
lookup, as most Linux distros do.
Note that this is a feature, not a bug, so if that's the cause of the
problem, there is nothing to do about it. You'd have to compile sbcl
with the toolchain of the foreign distro.
Cheers,
Konrad.
next prev parent reply other threads:[~2020-01-14 5:53 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 [this message]
2020-01-14 9:38 ` Pierre Neidhardt
2020-01-14 10:11 ` Konrad Hinsen
2020-01-14 10:25 ` Pierre Neidhardt
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
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=c2f7cc71-d672-e2f8-6280-664d26e680e1@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=39079@debbugs.gnu.org \
--cc=evan.straw99@gmail.com \
--cc=mail@ambrevar.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).