From: dsmich@roadrunner.com
To: "'Duy Nguyen'" <pclouds@gmail.com>
Cc: "'guile-devel@gnu.org'" <guile-devel@gnu.org>
Subject: Re: Replace ltdl with GLib's GModule
Date: Wed, 25 Mar 2020 12:11:24 +0000 [thread overview]
Message-ID: <72241d6990da52869a2de7230abd7810da263348@webmail> (raw)
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
> From: "Duy Nguyen"
>
> On Wed, Mar 25, 2020 at 5:24 AM Mike Gran wrote:
> >
> > In a fit of pique, I pushed a new branch of Guile to the repo
> > called wip-replace-ltdl-with-gmodule. It replaces the dynamic
linking
> > library libltdl from libtool with the analagous library GModule
> > from GLib. It was remarkably easy, and, after a cursory test
> > I was surprised to find that it seems to be working.
>
> So knee-jerk reaction, what does GModule do better than libltdl? Or
> perhaps why is libltdl "bad"?
Hopefully it will return something more detailed than "file not found"
for the many error cases that libtool lumps into that one error
message.
-Dale
[-- Attachment #2: Type: text/html, Size: 884 bytes --]
next reply other threads:[~2020-03-25 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 12:11 dsmich [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-25 14:58 Replace ltdl with GLib's GModule dsmich
[not found] <20200324222429.GA2587085.ref@spikycactus.com>
2020-03-24 22:24 ` 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
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=72241d6990da52869a2de7230abd7810da263348@webmail \
--to=dsmich@roadrunner.com \
--cc=guile-devel@gnu.org \
--cc=pclouds@gmail.com \
/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).