From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.5.8 beta available for testing.
Date: Thu, 29 Aug 2002 12:49:23 -0500 [thread overview]
Message-ID: <87hehdmu70.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20020829174235.GA19424@www> (tomas@fabula.de's message of "Thu, 29 Aug 2002 19:42:35 +0200")
tomas@fabula.de writes:
> On an additional note (as I'm testing Ralf's mod_guile), you
> have to set LD_LIBRARY_PATH for other applications using guile
> as well (in this case Apache), which is sometimes awkward.
>
> Is there another possibility to make libltdl work more
> reasonably? Are you taking patches? (oh, my goodness, for
> Guile 1.6.1+, of course ;-)
Well, there are some options wrt to libltdl, but most of them involve
modifying libltdl's search path (via its api, envt vars, etc.), but
then you have some fairly thorny questions about how that should be
done given the possibility that other shared libraries (or an app
guile's linked against) might be trying to do the same thing.
I think we'd hoped to wait until 1.7 development to try to come up
with a more correct solution, but it *is* a little awkward to require
people to set envt vars just to run guile when they're installing to
/usr/local.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
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 17:49 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
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 [this message]
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=87hehdmu70.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).