From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: my load path bug
Date: Mon, 12 Oct 2009 21:11:26 +0200 [thread overview]
Message-ID: <87iqekig0x.fsf@gnu.org> (raw)
In-Reply-To: A2015C79-60CD-4948-8A38-B6EDC50734B8@raeburn.org
Hi Ken,
Ken Raeburn <raeburn@raeburn.org> writes:
> 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.
Yes, I think that’s the way to go, since libguile-srfi-*,
libguilereadline*, etc. get installed to $(libdir), not $(pkglibdir).
If nobody objects, please commit it.
> Do we need programs to be able to link against them directly?
Yes since people may be explicitly linking against them (they’ve always
been under $(libdir)).
> Do we need non-guile programs to be able to find them with dlopen?
Yes.
> (Is it too late to consider changing it?)
Yes.
Thanks,
Ludo’.
next prev parent reply other threads:[~2009-10-12 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 15:50 my load path bug Ken Raeburn
2009-10-12 19:11 ` Ludovic Courtès [this message]
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=87iqekig0x.fsf@gnu.org \
--to=ludo@gnu.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).