From: Rob Browning <rlb@defaultvalue.org>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Purpose of guile-xxx executables?
Date: Thu, 12 Sep 2002 17:26:34 -0500 [thread overview]
Message-ID: <874rcu3kv9.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <m3znum52vj.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "12 Sep 2002 22:12:16 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> - something to do with platforms that only perform static linking.
I believe libtool solves this problem for you as long as you use it
properly (you'll have to see the docs, since I forget what "properly"
means). Libtool is supposed to arrange it so that on platforms
without shared libs, lt_dlopen/lt_dlsym, etc. still work.
--
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
prev parent reply other threads:[~2002-09-12 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 21:12 Purpose of guile-xxx executables? Neil Jerram
2002-09-12 21:48 ` Marius Vollmer
2002-09-12 22:26 ` Rob Browning [this message]
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=874rcu3kv9.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).