unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Fu-Gangqiang <lispor@163.com>
Cc: Guile bug <bug-guile@gnu.org>, Haible <bruno@clisp.org>, Bruno
Subject: Re: Can not work with libguile-2.0
Date: Fri, 18 Feb 2011 09:34:25 +0100	[thread overview]
Message-ID: <m31v353fn2.fsf@unquote.localdomain> (raw)
In-Reply-To: <1e640654.925f.12e338022b5.Coremail.lispor@163.com> (Fu-Gangqiang's message of "Thu, 17 Feb 2011 20:02:38 +0800 (CST)")

Hi Mark, Bruno, and Fu-Gangqiang,

Fu-Gangqiang writes:

> In manual section 2.3(Linking Guile into Programs)
>
> I follow the example,run it and have something wrong:
> ---->cut here<----
> $ gcc -o simple-guile simple-guile.c  `pkg-config --cflags --libs guile-2.0`
> $ ./simple-guile 
> ./simple-guile: error while loading shared libraries: libguile-2.0.so.22: cannot open shared object file: No such file or directory

Bruno Haible first brought up the issues here:

  http://lists.gnu.org/archive/html/libtool/2001-11/msg00050.html

I don't know of a consensus for the solution, so I'm copying him on the
mail here.  Bruno, what should we recommend in the manual that users do
to link to Guile, and produce an executable that correctly finds
libguile when it is run?

Thanks in advance,

Andy
-- 
http://wingolog.org/



  parent reply	other threads:[~2011-02-18  8:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 12:02 Can not work with libguile-2.0 Fu-Gangqiang
2011-02-17 13:02 ` Hans Aberg
2011-02-17 13:40 ` Fu-Gangqiang
2011-02-17 18:04 ` Mark Harig
2011-02-17 18:23 ` Mark Harig
2011-02-18  8:41   ` Andy Wingo
2011-02-17 19:08 ` Mark Harig
2011-02-18  8:53   ` Andy Wingo
2011-02-18 19:42     ` Mark Harig
2011-02-20 10:13       ` Andy Wingo
2011-02-18  1:39 ` Fu-Gangqiang
2011-02-18  8:34 ` Andy Wingo [this message]
2011-02-19 15:30   ` linking with libguile-2.0, rpath Bruno Haible
2011-02-20 10:58     ` Andy Wingo

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=m31v353fn2.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bruno@clisp.org \
    --cc=bug-guile@gnu.org \
    --cc=lispor@163.com \
    /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).