unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: libguile-ltdl
Date: Thu, 07 Oct 2004 10:11:32 -0500	[thread overview]
Message-ID: <87acuyy34r.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <16740.62645.775190.377226@byrd.xs4all.nl> (Han-Wen Nienhuys's message of "Thu, 7 Oct 2004 09:48:05 +0200")

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:

> what is versioned dlopen

The idea would be to add a function that would let you specify the
soname ("interface number") of the library you want to open, and that
function would then use the same algorithm that ld.so does when trying
to find a suitable library.

With the current dlopen, you can't do that.  If you say
dlopen("libfoo"), you have no control over whether you might get
libfoo.so.4, libfoo.so.12, or something else. So you have to resort to
other means, like putting the version in the library name,
i.e. libfoo4 (or libguile-srfi-srfi-4-v-1).  Then you can say
dlopen("libfoo4") and make sure you get libfoo "version" 4, but this
isn't as flexible as saying dlopen_ext("libfoo", 4), which ideally
would find the most recent version of libfoo satisfying interface 4
(just as ld.so does).

Of course we haven't gotten to the point of seeing what would be
involved here, especially cross-platform.  The most basic approach
(for at least linux/elf) would probably involve a search based on the
expected libtool soname.

> and for which GUILE release is it desired? 

No particular release in mind yet, though in the past we had talked
about it for 1.8.  However, now that we've worked around the issue by
putting the soname/version in the name for all of the libs that we
expect to dlopen, it's not as urgent, though it might be nice for
other projects that don't want to have to mangle their library names.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-10-07 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 22:36 libguile-ltdl Han-Wen Nienhuys
2004-09-28 22:54 ` libguile-ltdl Rob Browning
2004-10-06 22:44   ` libguile-ltdl Han-Wen Nienhuys
2004-10-07  1:31     ` libguile-ltdl Rob Browning
2004-10-07  7:48       ` libguile-ltdl Han-Wen Nienhuys
2004-10-07 15:11         ` Rob Browning [this message]
2004-10-07  7:52       ` libguile-ltdl Han-Wen Nienhuys
2004-10-07 15:17         ` libguile-ltdl Rob Browning
2004-10-07 18:35           ` libguile-ltdl Han-Wen Nienhuys
2004-10-18 16:28       ` libguile-ltdl Marius Vollmer
2004-10-18 16:32     ` libguile-ltdl 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=87acuyy34r.fsf@trouble.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).