From: Greg Troxel <gdt@ir.bbn.com>
Subject: 1.6.0 problems with libguilereadline-v-12 and fix
Date: Wed, 18 Sep 2002 16:33:11 -0400 [thread overview]
Message-ID: <20020918203311.3C5FA3F28@fnord.ir.bbn.com> (raw)
I built 1.6.0 on FreeBSD/i386 4.6-ish (tracking stable) with
--prefix=/usr/foo
I have (use-modules (ice-9 readline)) in my .guile, and guile failed
on startup trying to dynlink libguilereadline-v-12.
It seems that dynamic-link only looks in standard places.
For reasons I do not understand, guile/readline with the same /usr/foo
works on NetBSD 1.5.4_ALPHA/i386, even without the below patch. It
finds /usr/foo/lib/libguilereadline-v-12, but it seems incorrect of
libtool to look there.
This seems broken in two ways:
guile should look for its own libraries in exactly one place, the
location where it was installed.
guile should certainly look in $(prefix)/lib
So, I modified guile-readline/readline.scm to look in the right place
(although perhaps not only in the right place).
Perhaps a new procedure that is like dynamic link, but only looks in
the installed prefix, is in order, for internal use?
I suspect this problem affects the srfi code.
For you hard-core regression testers, perhaps testing with a
non-standard prefix is in order. For extra points, put defective
versions of the libs in /usr/local or some other 'normal' place.
Index: readline.scm
===================================================================
RCS file: /QUIST-CVS/guile/guile-readline/readline.scm,v
retrieving revision 1.1.1.2
retrieving revision 1.2
diff -u -r1.1.1.2 -r1.2
--- readline.scm 2002/07/19 17:56:31 1.1.1.2
+++ readline.scm 2002/09/18 20:19:17 1.2
@@ -36,7 +36,11 @@
(if (not (feature? 'readline))
(dynamic-call "scm_init_readline"
- (dynamic-link "libguilereadline-v-12")))
+ (dynamic-link
+ (string-append
+ (assq-ref %guile-build-info 'libdir)
+ "/"
+ "libguilereadline-v-12"))))
(if (not (feature? 'readline))
(scm-error 'misc-error
On NetBSD, guile mysteriously looks in the right place:
9315 guile CALL open(0x8102280,0,0x1b6)
9315 guile NAMI "/usr/lib/libguilereadline-v-12.la"
9315 guile RET open -1 errno 2 No such file or directory
9315 guile CALL open(0x80a2dc0,0,0x1b6)
9315 guile NAMI "libguilereadline-v-12.la"
9315 guile RET open -1 errno 2 No such file or directory
9315 guile CALL open(0x48059080,0,0x48052d20)
9315 guile NAMI "/usr/lib/libguilereadline-v-12.so"
9315 guile RET open -1 errno 2 No such file or directory
9315 guile CALL __stat13(0x48059100,0xbfbfce70)
9315 guile NAMI "/usr/foo/lib/libguilereadline-v-12.so"
9315 guile RET __stat13 0
9315 guile CALL open(0x48059100,0,0x48052d20)
9315 guile NAMI "/usr/foo/lib/libguilereadline-v-12.so"
9315 guile RET open 5
9315 guile CALL read(0x5,0xbfbfce3c,0x34)
env|grep foo turns up only /usr/foo/bin in PATH and /usr/foo/man in
MANPATH.
It can't be from PATH, since other dirs in PATH like /usr/gnats/bin
come first and /usr/gnats/lib is not tried.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2002-09-18 20:33 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 20:33 Greg Troxel [this message]
2002-09-18 21:14 ` 1.6.0 problems with libguilereadline-v-12 and fix 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
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=20020918203311.3C5FA3F28@fnord.ir.bbn.com \
--to=gdt@ir.bbn.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).