From: iyzsong@member.fsf.org (宋文武)
To: Alex Vong <alexvong1995@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: (dynamic-link "libm") doesn't work on guile
Date: Fri, 08 Jan 2016 11:27:49 +0800 [thread overview]
Message-ID: <87a8ogbvii.fsf@member.fsf.org> (raw)
In-Reply-To: <87bn8x65i9.fsf@gmail.com> (Alex Vong's message of "Thu, 07 Jan 2016 18:36:14 +0800")
Alex Vong <alexvong1995@gmail.com> writes:
> 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">
The `dynamic-link` will search and dlopen the shared library. The guile
from guix doesn’t search common places like ‘/usr/lib’, so you need to
set the environment variable `LD_LIBRARY_PATH` or `LTDL_LIBRARY_PATH`
explicitly to the directory contains `libm.so`.
by the way, since guile is linked with libm.so, we can just use
`(dynamic-link)` here.
well, I also find `(dynamic-link "libm-2.22")` work too, but it doesn’t
seem to be what we want to use.
next prev parent reply other threads:[~2016-01-08 3:28 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
2016-01-08 11:56 ` Alex Vong
2016-01-08 3:27 ` 宋文武 [this message]
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=87a8ogbvii.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--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).