From: Alex Vong <alexvong1995@gmail.com>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: help-guix@gnu.org
Subject: Re: (dynamic-link "libm") doesn't work on guile
Date: Fri, 08 Jan 2016 20:43:18 +0800 [thread overview]
Message-ID: <87bn8w9r89.fsf@gmail.com> (raw)
In-Reply-To: <87a8ogbvii.fsf@member.fsf.org> ("宋文武"'s message of "Fri, 08 Jan 2016 11:27:49 +0800")
iyzsong@member.fsf.org (宋文武) writes:
> 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.
I think it is weird. It seems only dynamic linking with "libc" or "libm"
fails, dynamic linking with external library like "libpcre2-8" or
anyhome-made shared library would work. And yes, "libc-2.22" and
"libm-2.22" also works for me. As you have mentioned, since guile is
already linked with "libc" and "libm", so it is pratically not a
problem. I am just wondering if it is a bug or the intended behavior.
Below are the selected output from running
`LD_DEBUG=all LD_LIBRARY_PATH="$HOME/.guix-profile/lib" guile`:
scheme@(guile-user)> (dynamic-link "libm")
29677:
29677: file=/home/alexvong1995/.guix-profile/lib/libm.so [0]; dynamically loaded by /home/alexvong1995/.guix-profile/lib/libltdl.so.7 [0]
29677:
29677: file=/gnu/store/5i87jzm90nw8j692y7z1j2qfx16h6ni3-guile-2.0.11/lib/libm.so [0]; dynamically loaded by /home/alexvong1995/.guix-profile/lib/libltdl.so.7 [0]
29677:
29677: file=/gnu/store/5i87jzm90nw8j692y7z1j2qfx16h6ni3-guile-2.0.11/lib/guile/2.0/extensions/libm.so [0]; dynamically loaded by /home/alexvong1995/.guix-profile/lib/libltdl.so.7 [0]
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.
scheme@(guile-user)> (dynamic-link "libc")
29677:
29677: file=/home/alexvong1995/.guix-profile/lib/libc.so [0]; dynamically loaded by /home/alexvong1995/.guix-profile/lib/libltdl.so.7 [0]
29677:
29677: file=/gnu/store/5i87jzm90nw8j692y7z1j2qfx16h6ni3-guile-2.0.11/lib/libc.so [0]; dynamically loaded by /home/alexvong1995/.guix-profile/lib/libltdl.so.7 [0]
29677:
29677: file=/gnu/store/5i87jzm90nw8j692y7z1j2qfx16h6ni3-guile-2.0.11/lib/guile/2.0/extensions/libc.so [0]; dynamically loaded by /home/alexvong1995/.guix-profile/lib/libltdl.so.7 [0]
ERROR: In procedure dynamic-link:
ERROR: In procedure dynamic-link: file: "libc", message: "file not found"
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
next prev parent reply other threads:[~2016-01-08 12:43 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 ` 宋文武
2016-01-08 10:07 ` Ludovic Courtès
2016-01-08 12:43 ` Alex Vong [this message]
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=87bn8w9r89.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=help-guix@gnu.org \
--cc=iyzsong@member.fsf.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).