From: Ken Raeburn <raeburn@raeburn.org>
To: guile-devel <guile-devel@gnu.org>
Subject: my load path bug
Date: Sat, 10 Oct 2009 11:50:56 -0400 [thread overview]
Message-ID: <A2015C79-60CD-4948-8A38-B6EDC50734B8@raeburn.org> (raw)
(Quick recap: I build and install to a non-standard directory, and
don't update LD_LIBRARY_PATH to cover it, and the "guile" binary has a
runtime load path specified that lets it find libguile, but Scheme
code tries to load other libraries and fails.)
Andy's patch (eb35012) adds $pkglibdir to the path searched for
libraries. That directory is $prefix/lib/guile; it contains a
subdirectory "1.9" and nothing else. The libguile-srfi-srfi-1-v-4.*
libraries guile searches for at startup are in $prefix/lib aka $libdir.
Changing SCM_LIB_DIR to be defined as $libdir instead of $pkglibdir is
easy enough, if the current location is where we want those
libraries. Do we need programs to be able to link against them
directly? Do we need non-guile programs to be able to find them with
dlopen? (Is it too late to consider changing it?)
Ken
Author: Ken Raeburn <raeburn@raeburn.org>
Date: Sat Oct 10 11:39:12 2009 -0400
Use libdir instead of pkglibdir for SCM_LIB_DIR.
diff --git a/libguile/Makefile.am b/libguile/Makefile.am
index acb26d9..7176c3c 100644
--- a/libguile/Makefile.am
+++ b/libguile/Makefile.am
@@ -601,7 +601,7 @@ libpath.h: $(srcdir)/Makefile.in $(top_builddir)/
config.status
@echo '#define SCM_PKGDATA_DIR "$(pkgdatadir)"' >> libpath.tmp
@echo '#define SCM_LIBRARY_DIR "$(pkgdatadir)/$
(GUILE_EFFECTIVE_VERSION)"'>>libpath.tmp
@echo '#define SCM_SITE_DIR "$(pkgdatadir)/site"' >> libpath.tmp
- @echo '#define SCM_LIB_DIR "$(pkglibdir)"' >> libpath.tmp
+ @echo '#define SCM_LIB_DIR "$(libdir)"' >> libpath.tmp
@echo '#define SCM_CCACHE_DIR "$(pkglibdir)/$
(GUILE_EFFECTIVE_VERSION)/ccache"' >> libpath.tmp
@echo '#define SCM_EFFECTIVE_VERSION "$(GUILE_EFFECTIVE_VERSION)"'
>> libpath.tmp
@echo '#define SCM_BUILD_INFO { \' >> libpath.tmp
next reply other threads:[~2009-10-10 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 15:50 Ken Raeburn [this message]
2009-10-12 19:11 ` my load path bug Ludovic Courtès
2009-10-19 19:00 ` Andy Wingo
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=A2015C79-60CD-4948-8A38-B6EDC50734B8@raeburn.org \
--to=raeburn@raeburn.org \
--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).