unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Replace ltdl with GLib's GModule
Date: Fri, 27 Mar 2020 10:03:48 -0700	[thread overview]
Message-ID: <20200327170348.GA11226@spikycactus.com> (raw)
In-Reply-To: <83imiq7wrm.fsf@gnu.org>

On Fri, Mar 27, 2020 at 04:27:57PM +0300, Eli Zaretskii wrote:
> > I think we should either fix ltdl (probably less work than porting Guile
> > to GModule, but also less exciting) or have a very basic wrapper around
> > dlopen instead of using ltdl (I think Andy had made experiments in that
> > direction.)
> 
> If you drop ltdl, the MinGW port of Guile will be broken, as dlopen
> there is not guaranteed to exist (it exists in one flavor of MinGW,
> but not in the other, which is the most popular one, AFAIK).
> 
> So my recommendation would be to fix ltdl.
> 

I must be said that the libtool mailing list appears extremely
conservative with respect to change.

I haven't evaluated it on a technical level, but I do see small
patches in GModule to handle things like UWP, while the last technical
change to libltdl was probably around 2011.

If GModule is up to date, it looks like there are only three families
of dynamic linking that remain: dlopen for UNIX-Likes, AIX's dlopen of
AIX-format .ar archives, and Microsoft's LoadLibrary.  MacOS's dyld is
gone.

Maybe when I have a moment, I'll strip GLib from GModule to see what
it looks like, or perhaps see what new information GModule contains
that could be flowed down to ltdl.  Not that I expect Guile to
necessarily incorporate it, but, because I find it interesting.

But, I don't see myself as finding any fun in interacting with the
libtool mailing list, so I probably won't do that.

Regards,
Mike Gran




  reply	other threads:[~2020-03-27 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200324222429.GA2587085.ref@spikycactus.com>
2020-03-24 22:24 ` Replace ltdl with GLib's GModule Mike Gran
2020-03-25  9:33   ` Duy Nguyen
2020-03-25 12:41     ` Mike Gran
2020-03-27 12:01   ` Ludovic Courtès
2020-03-27 13:27     ` Eli Zaretskii
2020-03-27 17:03       ` Mike Gran [this message]
2020-03-25 12:11 dsmich
  -- strict thread matches above, loose matches on Subject: below --
2020-03-25 14:58 dsmich

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=20200327170348.GA11226@spikycactus.com \
    --to=spk121@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).