unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-user@gnu.org
Subject: Re: 1.6.0 problems with libguilereadline-v-12 and fix
Date: 08 Oct 2002 23:26:06 +0200	[thread overview]
Message-ID: <8765wcwrkh.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3elb617dv.fsf@multivac.cwru.edu>

prj@po.cwru.edu (Paul Jarc) writes:

> > Why is that better than always and system-wide prepending $(libdir) to
> > LD_LIBRARY_PATH?
> 
> It's less error-prone.  LD_LIBRARY_PATH can be gotten wrong after
> installation - by users.  Whereas if Guile looks in libdir
> automatically (as it could with a fixed libltdl), then as long as
> installation was done correctly, users can't shoot themselves in the
> foot that way.

But that might come back to hunt them later.  Guile will be able to
magically find libraries that can't otherwise be found.  I really do
strongly believe that when you install software into /usr/local but
the system can't find shared libraries in /usr/local/lib by default,
then the system is not correctly configured, not the package that has
been installed into /usr/local.  Same with any other prefix.

> > You do need a long PATH already, no?
> 
> No.  All commands are symlinked in /command, so that's the only
> directory in my global PATH.  But that's a wart, it's one more thing
> to have to maintain, and I don't want to have to create a similar one
> for libraries.

Everything thing else will be a bigger wart, in my opinion.  You might
not want to deal with it, but Guile is not the place to take care of
it, either.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2002-10-08 21:26 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 20:33 1.6.0 problems with libguilereadline-v-12 and fix Greg Troxel
2002-09-18 21:14 ` Marius Vollmer
2002-09-18 21:53   ` Paul Jarc
2002-09-18 22:40     ` Rob Browning
2002-09-18 22:43       ` Paul Jarc
2002-09-19  3:22         ` Rob Browning
2002-09-19  4:13           ` Robert Uhl <ruhl@4dv.net>
2002-09-19 10:03           ` rm
2002-09-19 15:02             ` Rob Browning
2002-09-19 15:18               ` Paul Jarc
2002-09-19 15:27               ` rm
2002-09-19 18:29                 ` Rob Browning
2002-10-03 16:03                 ` Marius Vollmer
2002-10-03 15:56             ` Marius Vollmer
2002-10-03 17:22               ` Paul Jarc
2002-10-04 11:58                 ` Marius Vollmer
2002-10-03 19:19               ` tomas
2002-10-04 12:04                 ` Marius Vollmer
2002-10-04 13:04                   ` rm
2002-10-08 21:16                     ` Marius Vollmer
2002-10-08 21:54                       ` Dale P. Smith
2002-10-09  6:47                       ` tomas
2002-09-19 10:11           ` rm
2002-09-19 15:10           ` Paul Jarc
2002-09-19 21:21           ` Neil Jerram
2002-09-19 22:06             ` Rob Browning
2002-09-19 22:17               ` Paul Jarc
2002-09-19 23:13                 ` Rob Browning
2002-09-19  4:02         ` Thien-Thi Nguyen
2002-09-19 16:17           ` Paul Jarc
2002-09-19 18:52             ` Thien-Thi Nguyen
2002-09-19 19:33               ` Paul Jarc
2002-09-19 19:58                 ` Thien-Thi Nguyen
2002-09-19 22:17                   ` Thien-Thi Nguyen
2002-09-20  1:28                     ` Thien-Thi Nguyen
2002-09-20 15:45                       ` Paul Jarc
2002-10-03 15:38     ` Marius Vollmer
2002-10-04 16:43       ` Paul Jarc
2002-10-08 21:26         ` Marius Vollmer [this message]
2002-10-08 21:38           ` Paul Jarc
2002-10-08 22:47             ` Marius Vollmer
2002-10-09  4:34               ` Paul Jarc
2002-10-09  6:51               ` tomas
2002-09-19 13:17   ` Arno Peters
2002-09-19 14:07     ` Rob Browning
2002-10-03 16:06     ` Marius Vollmer
2002-10-03 19:44       ` Rob Browning
2002-09-19 13:43   ` Greg Troxel
2002-09-19 14:53     ` Rob Browning
2002-09-19 15:57       ` Paul Jarc
2002-09-19 18:47         ` Rob Browning
2002-09-19 19:32           ` Paul Jarc
2002-09-19 21:07             ` Rob Browning
2002-09-20 11:47       ` Greg Troxel
2002-09-20 12:04       ` Greg Troxel
2002-09-20 15:23         ` Rob Browning
2002-09-20 22:47           ` Paul Jarc
2002-09-21  3:00             ` Rob Browning
2002-09-21 15:46             ` Robert Uhl <ruhl@4dv.net>
2002-09-21 21:45               ` Paul Jarc
2002-09-23  4:35                 ` Robert Uhl <ruhl@4dv.net>
2002-09-23 15:47                   ` Paul Jarc
2002-09-23 19:20                     ` Robert Uhl <ruhl@4dv.net>
2002-09-23 20:06                       ` Paul Jarc
2002-09-23 21:29                         ` Eric E Moore
2002-09-23 21:37                           ` Paul Jarc
2002-09-20 17:59         ` Rob Browning
2002-09-20 21:32           ` Paul Jarc
2002-09-20 20:27         ` Paul Jarc
2002-09-20 20:42         ` Thien-Thi Nguyen
2002-09-20 21:16           ` Paul Jarc
2002-09-20 21:43             ` Paul Jarc
2002-09-21  1:56             ` Thien-Thi Nguyen
2002-09-21 21:51               ` Paul Jarc
2002-09-25  6:09                 ` Thien-Thi Nguyen
2002-09-22 18:52         ` Gary Houston
2002-09-23  1:50           ` Rob Browning
2002-10-03 16:33           ` Marius Vollmer
2002-10-03 17:51         ` Marius Vollmer
2002-10-03 17:37     ` Marius Vollmer

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=8765wcwrkh.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --cc=guile-user@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).