unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Evan Straw <evan.straw99@gmail.com>
Cc: 39079@debbugs.gnu.org
Subject: bug#39079: SBCL CFFI from Guix unable to find dynamic libraries
Date: Mon, 13 Jan 2020 23:22:28 +0100	[thread overview]
Message-ID: <87o8v7yp23.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87v9pfm2fq.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]

Hi!

Evan Straw <evan.straw99@gmail.com> writes:

> However, the thing that still doesn't appear to be working right is loading
> libraries from the foreign distro. I get the same behavior as before when
> attempting to load a library under the foreign distro's library directory
> (/usr/lib/x86_64-linux-gnu): It loads the library itself but fails upon trying
> to load any dependencies, even if they are in the same directory.

What are "dependencies" here?
Can you provide a full recipe of what you are trying to do, including
your .sbclrc and the Lisp code snippets you've run to test this?

> Ideally, I would just install the libraries I need from Guix, but I
> specifically want to interface with a library from the system, in this
> case PulseAudio (I've just been using libcurl as a test to make sure
> it works).

Does it work for the libraries installed with Guix?

> I did some investigation and tried both installing just CFFI from another
> source, and then SBCL itself. Installing CFFI from Quicklisp but keeping SBCL
> from Guix gave the same behavior and was unable to load dependencies of the
> library. Installing SBCL from APT and CFFI from Quicklisp was able to load the
> library and all dependencies with no issues. From this, I'm wondering if it's a
> problem with SBCL itself instead of CFFI?

This seems to be a red herring, as Guix does not change how CFFI loads
libraries.  The only thing that changes is where the libraries are found
with Guix packages.

Let's see what we can reproduce with your examples! :)

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-01-13 22:23 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 [this message]
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
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=87o8v7yp23.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=39079@debbugs.gnu.org \
    --cc=evan.straw99@gmail.com \
    /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).