From: Greg Troxel <gdt@ir.bbn.com>
Subject: dynamic linking problems when using --prefix, perhaps solved
Date: Wed, 13 Mar 2002 09:25:48 -0500 [thread overview]
Message-ID: <20020313142548.357963C24@fnord.ir.bbn.com> (raw)
I am having the same dynamic linking problems as others:
lab gdt 157 ~/QUIST-current/guile > /usr/quist/bin/guile
ERROR: In procedure dynamic-link:
ERROR: file: "libguilereadline", message: "file not found"
lab gdt 158 ~/QUIST-current/guile > sudo ldconfig -m /usr/quist/lib
lab gdt 159 ~/QUIST-current/guile > /usr/quist/bin/guile
ERROR: In procedure dynamic-link:
ERROR: file: "libguilereadline", message: "file not found"
IMHO there should be some way to pass @libdir@ to libtool's dlopen, so
that guile can search in its installed directory first.
The following worked, but it is kludgy:
LTDL_LIBRARY_PATH=/usr/quist/lib /usr/quist/bin/guile
So, I added $libdir to the default path in libltdl/configure
(patching configure rather than configure.in since I have an old
autoconf version)
Index: configure
===================================================================
RCS file: /QUIST-CVS/guile/libltdl/configure,v
retrieving revision 1.1.1.1
diff -u -u -r1.1.1.1 configure
--- configure 2002/03/04 23:43:29 1.1.1.1
+++ configure 2002/03/13 14:16:06
@@ -5479,7 +5479,7 @@
shlibpath_overrides_runpath=unknown
version_type=none
dynamic_linker="$host_os ld.so"
-sys_lib_dlsearch_path_spec="/lib /usr/lib"
+sys_lib_dlsearch_path_spec="$libdir /lib /usr/lib"
sys_lib_search_path_spec="/lib /usr/lib /usr/local/lib"
case $host_os in
and now /usr/quist/bin/guile works without path hackery.
I noticed that before this change, /usr/quist/bin/guile would find the
libguilereadline library if it was in the current directory. This
seems like a '. in $PATH' vulnerability.
Alternatively, the scheme code that links libguilereadline could pass
in the entire path, rather than just the filename. This would ensure
that guile links only a matching libguilereadline. There are a lot of
systems on which guile 1.4 and 1.5.x will have to coexist - I want to
use 1.5.6 for new stuff but gnome pulls in 1.4.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2002-03-13 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 14:25 Greg Troxel [this message]
2002-04-24 20:48 ` dynamic linking problems when using --prefix, perhaps solved 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=20020313142548.357963C24@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).