From: ludo@gnu.org (Ludovic Courtès)
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 14:51:21 +0100 [thread overview]
Message-ID: <87vb74ji1y.fsf@gnu.org> (raw)
In-Reply-To: <87bn8w9r89.fsf@gmail.com> (Alex Vong's message of "Fri, 08 Jan 2016 20:43:18 +0800")
Alex Vong <alexvong1995@gmail.com> skribis:
> 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.
I think that’s because libm.so and libc.so are linker scripts, whereas
libm-2.22.so and libc-2.22.so are the actual ELF files:
--8<---------------cut here---------------start------------->8---
$ cat ~/.guix-profile/lib/libm.so
/* GNU ld script
*/
OUTPUT_FORMAT(elf64-x86-64)
GROUP ( /gnu/store/qv7bk62c22ms9i11dhfl71hnivyc82k2-glibc-2.22/lib/libm.so.6 AS_NEEDED ( /gnu/store/qv7bk62c22ms9i11dhfl71hnivyc82k2-glibc-2.22/lib/libmvec.so.1 ) )
$ cat ~/.guix-profile/lib/libc.so
/* GNU ld script
Use the shared library, but some functions are only in
the static library, so try that secondarily. */
OUTPUT_FORMAT(elf64-x86-64)
GROUP ( /gnu/store/qv7bk62c22ms9i11dhfl71hnivyc82k2-glibc-2.22/lib/libc.so.6 /gnu/store/qv7bk62c22ms9i11dhfl71hnivyc82k2-glibc-2.22/lib/libc_nonshared.a AS_NEEDED ( /gnu/store/qv7bk62c22ms9i11dhfl71hnivyc82k2-glibc-2.22/lib/ld-linux-x86-64.so.2 ) )
--8<---------------cut here---------------end--------------->8---
Ludo’.
next prev parent reply other threads:[~2016-01-08 13:51 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
2016-01-08 13:51 ` Ludovic Courtès [this message]
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=87vb74ji1y.fsf@gnu.org \
--to=ludo@gnu.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).