From: 陶青云 <qingyun.tao@tophant.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Question: link to wrong library
Date: Sun, 21 Jan 2018 22:44:14 +0800 [thread overview]
Message-ID: <tencent_455F7D9F21F041EB107A2C51@qq.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Hi. I'm new to guile. I compiled it from source without `make install`.
I write a simple C file and use the flowing command to compile it.
`gcc -pthread -I. -L ./libguile/.libs -lguile-2.2 -lgc test.c`
it successed. but the a.out is always link to my system guile library.
$ ldd ./a.out
linux-vdso.so.1 (0x00007fffc259b000)
libguile-2.2.so.1 => /usr/lib/libguile-2.2.so.1 (0x00007fa90f9fe000)
libgc.so.1 => /usr/lib/libgc.so.1 (0x00007fa90f794000)
even I do the flowing:
$ cp libguile/.libs/libguile-2.2.so.1.3.0 libguile/.libs/libguile-2.5.so
$ gcc -pthread -I. -L ./libguile/.libs -lguile-2.5 -lgc test.c # it successed
$ ldd ./a.out
linux-vdso.so.1 (0x00007ffd283e0000)
libguile-2.2.so.1 => /usr/lib/libguile-2.2.so.1 (0x00007f83c71cc000)
libgc.so.1 => /usr/lib/libgc.so.1 (0x00007f83c6f62000)
Could someone give me some tips. Thanks.
[-- Attachment #2: Type: text/html, Size: 1494 bytes --]
next reply other threads:[~2018-01-21 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 14:44 陶青云 [this message]
2018-01-22 1:07 ` Question: link to wrong library Nala Ginrut
2018-01-22 4:58 ` Chaos Eternal
2018-01-22 11:30 ` 陶青云
2018-01-22 11:36 ` Chaos Eternal
2018-01-22 12:56 ` 陶青云
2018-01-22 13:10 ` Chaos Eternal
2018-01-22 12:59 ` Nala Ginrut
2018-01-23 1:14 ` Matt Wette
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_455F7D9F21F041EB107A2C51@qq.com \
--to=qingyun.tao@tophant.com \
--cc=guile-devel@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).