From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: 64723@debbugs.gnu.org
Cc: spk121@yahoo.com
Subject: bug#64723: [PATCH] Improve DLL search strategy for load-foreign-library
Date: Sat, 09 Sep 2023 07:44:46 +0200 [thread overview]
Message-ID: <87wmwzq4s1.fsf@gnu.org> (raw)
In-Reply-To: <1043899963.3392487.1694100835593@mail.yahoo.com> (Mike Gran via's message of "Thu, 7 Sep 2023 15:33:55 +0000 (UTC)")
Mike Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language writes:
Hello Mike,
>> The new non-libltdl foreign library loading algorithm from 3.0.6
>> fails to cover common cases regarding how libtool names and installs
>> DLL files. Notably, it fails to recognize when libtool has added the
>> major version number into the filename itself, such as libfoo-1.dll
>> Also, it does not search in binary directories and the PATH for DLL
>> files, where libtool is likely to install DLLs.
>
> Hi All-
>
> This is the first of a dozen patches to make Win32 minimally viable
> again. This patch specifically removes a regression introduced in 3.0.6
> described above.
>
> If I hear no objection, I'm going to rebase and push
> in a week or two.
Very much appreciated!
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
prev parent reply other threads:[~2023-09-09 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vriuedl4qtxt.fsf.ref@yahoo.com>
2023-07-19 6:47 ` bug#64723: load-foreign-library has incomplete support for libtool-generated DLLs Michael Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2023-06-02 23:28 ` bug#64723: [PATCH] Improve DLL search strategy for load-foreign-library Michael Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2023-09-07 15:33 ` Mike Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2023-09-09 5:44 ` Janneke Nieuwenhuizen [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=87wmwzq4s1.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=64723@debbugs.gnu.org \
--cc=spk121@yahoo.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).