From: tomas@fabula.de
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.5.8 beta available for testing.
Date: Thu, 29 Aug 2002 12:29:43 +0200 [thread overview]
Message-ID: <20020829102943.GB18398@www> (raw)
In-Reply-To: <87adn9plqf.fsf@raven.i.defaultvalue.org>
On Mon, Aug 26, 2002 at 12:34:48PM -0500, Rob Browning wrote:
>
> We are pleased to annouce the availability of Guile 1.5.8 for testing.
> Please report problems to guile-devel@gnu.org or bug-guile@gnu.org.
>
[...]
> - Make sure LD_LIBRARY_PATH doesn't include anything
> unnecessary -- though at the moment it (or
> LTDL_LIBRARY_PATH) will need to include guile's lib
> directory if that directory is not already in the normal
> places libltdl looks.
Test results on an oldish Debian Woody on Intel (so pretty vanilla):
after the usual unpacking, ./configure, make, make install make check
(which seems satisfied), and make install (all defaults, so installation
goes to /usr/local/), calling guile:
| spu@flunda:~/guile/guile-1.5.8$ guile
| ERROR: In procedure dynamic-link:
| ERROR: file: "libguilereadline-v-12", message: "file not found"
(there were some old guile libs in /usr/lib. Removing them didn't change
anything).
An strace reveals where guile is looking for this lib. Here's the bit which
looks relevant to me:
| open("/lib/libguilereadline-v-12.la", O_RDONLY) = -1 ENOENT (No such file or directory)
| open("/usr/lib/libguilereadline-v-12.la", O_RDONLY) = -1 ENOENT (No such file or directory)
| open("libguilereadline-v-12.la", O_RDONLY) = -1 ENOENT (No such file or directory)
Setting LD_LIBRARY_PATH seems to fix the problem for me:
| spu@flunda:~$ LD_LIBRARY_PATH=/usr/local/lib guile
| guile> (version)
| "1.5.8"
| guile>
NOTE: Yes, I have /usr/local/lib in /etc/ld.so.conf. Careful as I am ;-) I ran
/sbin/ldconfig, which didn't change anything (and the strace shows that guile finds
its other libs unter /usr/local/lib anyway, it's just this libguilereadline-v-12)
Thanks for the work, and I'm jumping excitedly up and down in expectation of
guile 1.6 :-)
Regards
-- tomas
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-29 10:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 17:34 Guile 1.5.8 beta available for testing Rob Browning
2002-08-27 9:06 ` Lars J. Aas
2002-08-28 16:28 ` Marius Vollmer
2002-08-29 7:59 ` Lars J. Aas
2002-08-31 12:01 ` Marius Vollmer
2002-09-02 11:38 ` Lars J. Aas
2002-08-29 10:29 ` tomas [this message]
2002-08-29 16:22 ` Rob Browning
2002-08-29 17:18 ` tomas
2002-08-29 17:42 ` tomas
2002-08-29 17:49 ` Rob Browning
2002-08-29 18:04 ` Lynn Winebarger
2002-08-29 18:55 ` Marius Vollmer
2002-08-29 19:17 ` Lynn Winebarger
2002-08-29 19:24 ` Lynn Winebarger
2002-08-29 19:58 ` Marius Vollmer
2002-08-31 16:45 ` tomas
2002-08-29 18:49 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2002-08-28 13:34 Sven Hartrumpf
2002-08-28 14:21 ` Marius Vollmer
2002-08-28 14:38 ` Sven Hartrumpf
2002-08-28 15:34 ` Marius Vollmer
2002-08-28 16:21 ` Lynn Winebarger
2002-08-28 18:18 ` Han-Wen Nienhuys
2002-08-28 21:09 ` Sven Hartrumpf
2002-08-28 22:43 ` Han-Wen Nienhuys
2002-09-03 7:33 ` Sven Hartrumpf
2002-09-04 11:08 ` Han-Wen Nienhuys
2002-09-04 14:43 ` Sven Hartrumpf
2002-09-05 12:08 ` Han-Wen Nienhuys
2002-09-05 19:52 ` Sven Hartrumpf
2002-09-03 11:14 ` Sven Hartrumpf
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=20020829102943.GB18398@www \
--to=tomas@fabula.de \
--cc=guile-devel@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).