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: Sun, 16 Jan 2011 14:38:27 -0500 [thread overview]
Message-ID: <8CD83CC14D7A7E0-1624-1AA70@webmail-m056.sysops.aol.com> (raw)
In-Reply-To: <87d3nxgaf9.fsf@ossau.uklinux.net>
>
> I'd say too OS-dependent; or more to do with how guile should be
> properly installed, than how to use it once it is installed.
>
> But on the other hand, I might be misunderstanding what you had in
mind;
> if you'd like to propose some specific text...
>
If a user has followed the instructions in the section "Obtaining and
Installing Guile", and installed guile in the "/usr/local/" directory
tree, then, on systems that use the dynamic linker/loader ld.so or
ld-linux.so*, the instructions in the section "Linking Guile into
Programs" will fail because the new program 'simple-guile' will not be
able to locate the shared library 'libguile-2.0.so*'.
Here is some suggested text for the ENVIRONMENT and SEE ALSO sections
of the guile.1 manual page:
ENVIRONMENT
LD_LIBRARY_PATH
This variable may need to be set on operating systems that use
the dynamic linker/loader ld.so/ld-linux.so* to specify where
the shared libraries that are provided by Guile can be found.
The variable should provide a colon-separated list of
directories.
For example, in the bash shell the following assignment may be
used:
export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH
More information about this variable can be found in the
documentation for the dynamic linker/loader (ld.so(8) or
ld-linux.so(8)).
SEE ALSO
ld.so(8), ld-linux.so(8)
Another item of information that would be useful to add to the guile.1
manual page would be the date and version of Guile that the manual
page describes. For example, the Emacs manual page lists the date
that it is effective and the version. This appears at the bottom of
the manual page, even though the directive describing it appears at
the top of emacs.1:
.TH EMACS 1 "2007 April 13" "GNU Emacs 23.2"
Likewise, Guile might have:
.TH GUILE 1 "2011 Jan 16" "GNU Guile 2.0"
--
next prev parent reply other threads:[~2011-01-16 19:38 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 [this message]
2011-01-19 19:50 ` Ken Raeburn
2011-01-20 2:31 ` Mark Harig
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=8CD83CC14D7A7E0-1624-1AA70@webmail-m056.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).