From: Mike Gran <spk121@yahoo.com>
To: "Hannes Müller" <h.c.f.mueller@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: guile 3.0.8: readline does not work - patch with also other fixes
Date: Tue, 4 Oct 2022 16:07:38 -0700 [thread overview]
Message-ID: <Yzy8uoZU/w1STioR@spikycactus.com> (raw)
In-Reply-To: <0731d827b9d5f2261764808a2ea6617592169883.camel@gmail.com>
On Tue, Oct 04, 2022 at 08:06:00PM +0200, Hannes M�ller wrote:
> Hi Guile-Maintainer,
> Hi Marco Atzeri,
>
> with e.g. guile 3.0.8-1 I noticed serveral problems.
>
> Most important one is not working readline support. You may check in
> guile via e.g.:
> (begin (use-modules (ice-9 readline))(activate-readline))
>
> With e.g. guile3.0-3.0.8-1.src the shared library guile-readline-0.dll
> is created on Cygwin but guile-readline.dll is expected. This results
> from guile since 3.0.6 does not load foreign libraries via libltdl.
Hannes-
Hi. I can speak speak for upstream Guile on that, I guess. When the
core Guile maintainers dumped libltdl, I was the one that wrote the
Guile code that converted GNU/Linux shared object names to Cygwin DLL
names, and I forgot to properly account for version numbers in Cygwin
DLL names.
The code that does "libfoo.so" to "cygfoo.dll"...
On Linux, "libfoo.so" is usually a link to a more specific
"libfoo.so.x" so Guile doesn't have to search for the most recent
revision.
I could change that code so that the code that searches for "libfoo.so"
actually searches for anything named "cygfoo.dll" and "cygfoo-??.dll",
but I'd need someone on Cygwin to explain to me how that search should
be. Is the '??' in cygfoo-?? always numeric? How many digits can
it be? I'm assuming the highest number has priority.
Should "cygfoo.dll" outrank "cygfoo-1.dll", or is it the opposite?
Is there some Cygwin library function that will do this search for me
that I should know about?
As for the other patches to upstream Guile, if no one else is
working on it, I'll see what I can do.
But in the meantime, if Cygwin wants to incorporate your patch
to '-avoid-version' in guile-readline, that's the best solution
for 3.0.8.
Thanks,
Mike Gran
next prev parent reply other threads:[~2022-10-04 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 18:06 Hannes Müller
2022-10-04 23:07 ` Mike Gran [this message]
2022-10-06 19:13 ` Hannes Müller
2022-10-08 7:30 ` Brian Inglis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yzy8uoZU/w1STioR@spikycactus.com \
--to=spk121@yahoo.com \
--cc=cygwin@cygwin.com \
--cc=h.c.f.mueller@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).