unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark Harig <idirectscm@aim.com>
To: bug-guile@gnu.org
Subject: Re: Missing and out-of-date information in guile.1, the Guile man page
Date: Wed, 19 Jan 2011 21:31:10 -0500	[thread overview]
Message-ID: <8CD86613C075756-1D10-34A6@webmail-m067.sysops.aol.com> (raw)
In-Reply-To: <3D05815A-48F6-43E8-8A9D-5415972D032F@raeburn.org>

On Wed, Jan 19, 2011 at 02:50:29PM -0500, Ken Raeburn wrote:

>
> I think the right answer for that is not to tell people that they
> have to set environment variables in order to run Guile programs,
> but to tell developers how to link programs properly so that they
> find the library at run time.  This tends to be somewhat
> platform-dependent, but often arguments like "-R" or "-rpath" are
> needed; libtool should just Do The Right Thing, if it's used.  I'm
> less familiar with pkg-config, but expect it should be have
> similarly.  In fact, the man page for pkg-config on my system (Mac
> OS X with MacPorts installed) says the "--libs-only-L" option
> "prints the -L/-R part" of the link options, which suggests to me
> that pkg-config is indeed supposed to be printing options to set the
> run-time load path.  If it's not doing that for you, then we should
> figure out why not.
>
> In short, don't document how to work around a bug, if you can just
> fix the bug. :-)
>

OK.  Whichever approach is taken, readers of the Guile Reference
Manual should be able to follow the steps described and have those
steps work, that is, the generated program should run.  My aim is to
help get Guile 2.0 have as few defects as possible before it is
released so that when new users try it, they have an error-free first
pass.



  reply	other threads:[~2011-01-20  2:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 21:58 Missing and out-of-date information in guile.1, the Guile man page Mark Harig
2011-01-15 20:48 ` Neil Jerram
2011-01-16 19:38   ` Mark Harig
2011-01-19 19:50     ` Ken Raeburn
2011-01-20  2:31       ` Mark Harig [this message]
2011-01-24 21:07       ` Andy Wingo
2011-01-16 23:23   ` Mark Harig
2011-01-24 21:54     ` Andy Wingo
2011-01-25  7:05       ` Mark Harig
2011-03-04  9:35         ` Andy Wingo
     [not found]           ` <8CDA8E5BB95D253-584-D4A3@webmail-m087.sysops.aol.com>
2011-03-05 19:29             ` Andy Wingo
2011-01-24 21:06 ` Andy Wingo
2011-01-24 23:05   ` Mark Harig

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=8CD86613C075756-1D10-34A6@webmail-m067.sysops.aol.com \
    --to=idirectscm@aim.com \
    --cc=bug-guile@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).