unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org, lispor@163.com
Subject: Re: Can not work with libguile-2.0
Date: Fri, 18 Feb 2011 09:53:27 +0100	[thread overview]
Message-ID: <m3sjvl206w.fsf@unquote.localdomain> (raw)
In-Reply-To: <8CD9CED2114C060-235C-1E45A@Webmail-m118.sysops.aol.com> (Mark Harig's message of "Thu, 17 Feb 2011 14:08:00 -0500")

On Thu 17 Feb 2011 20:08, Mark Harig <idirectscm@aim.com> writes:

> The command listed in section 2.4 "Writing Guile Extensions"
> should follow the pattern used in section 2.3 "Linking Guile into
> Programs," namely, add the 'pkg-config' command to provide the
> appropriate command-line options for the preprocessor, compiler, and
> linker.

Really?  It doesn't seem to be necessary to actually link to libguile
there.

> In addition, the manual should mention that the environment
> variable 'PKG_CONFIG_PATH' needs to be set before invoking the
> compiler.  Something like the following needs to be added, along with
> some explanatory text:
>
>  $ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH

Well that isn't quite right, as /usr/local/lib isn't the right place for
libguile-2.0 on many systems.  It's lib64 on my fedora machine.

I guess we will have to add a section on install prefixes, and the
relation between -rpath, libtool, PKG_CONFIG_PATH, and guile-config.
Then further compile/link examples can refer back (or forwards) to it.
Perhaps it would be best to assume that Guile is system-installed, and
note that if linking fails, see some section at the end of libguile.texi
that discusses these issues.

What do you think?

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-02-18  8:53 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 [this message]
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
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=m3sjvl206w.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=idirectscm@aim.com \
    --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).