From: Leo Famulari <leo@famulari.name>
To: Alex Vong <alexvong1995@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: (dynamic-link "libm") doesn't work on guile
Date: Thu, 7 Jan 2016 21:30:49 -0500 [thread overview]
Message-ID: <20160108023049.GA26535@jasmine> (raw)
In-Reply-To: <87bn8x65i9.fsf@gmail.com>
On Thu, Jan 07, 2016 at 06:36:14PM +0800, Alex Vong wrote:
> Hi people,
>
>
> I got the following error message when trying to dlopen a shared library
> in ~/guix-profile/bin/guile installed by guix:
>
> scheme@(guile-user)> (dynamic-link "libm")
> ERROR: In procedure dynamic-link:
> ERROR: In procedure dynamic-link: file: "libm", message: "file not found"
>
> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
>
>
> I think it is a guix-specific problem since /usr/bin/guile installed by
> debian works fine:
>
> scheme@(guile-user)> (dynamic-link "libm")
> $1 = #<dynamic-object "libm">
>
>
> Any idea?
Usually when a Debian package works while the Guix package fails, I
examine the Debian packaging, especially the file at 'debian/rules'.
You can find those on the package web page [0] as the [...]debian.tar.xz
file and surely through some command-line tool.
[0] Make sure to select your Debian release (Jessie, Stretch, etc):
https://packages.debian.org/stretch/guile-2.0
>
> Thanks,
> Alex
>
next prev parent reply other threads:[~2016-01-08 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 10:36 (dynamic-link "libm") doesn't work on guile Alex Vong
2016-01-08 2:30 ` Leo Famulari [this message]
2016-01-08 11:56 ` Alex Vong
2016-01-08 3:27 ` 宋文武
2016-01-08 10:07 ` Ludovic Courtès
2016-01-08 12:43 ` Alex Vong
2016-01-08 13:51 ` Ludovic Courtès
2016-01-09 14:08 ` Alex Vong
2016-01-09 17:39 ` Ludovic Courtès
2016-01-10 6:05 ` Alex Vong
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=20160108023049.GA26535@jasmine \
--to=leo@famulari.name \
--cc=alexvong1995@gmail.com \
--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).