From: "Hannes Müller" <h.c.f.mueller@gmail.com>
To: cygwin@cygwin.com
Subject: guile 3.0.8: readline does not work - patch with also other fixes
Date: Tue, 04 Oct 2022 20:06:00 +0200 [thread overview]
Message-ID: <0731d827b9d5f2261764808a2ea6617592169883.camel@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
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.
With attached proposed 3.0.8-2.src, I fixed not only readline support
but also:
- gettext-devel and libgc-devel added to BUILD_REQUIRES
- libgmp-devel added to libguile3_0_devel_REQUIRES
- Removed --includedir=/usr/include/guile/3.0 from CYGCONF_ARGS since
it resulted in /usr/include/guile/3.0/guile/3.0. So in fact --
includedir should be only /usr/include, which is the default
Since I personally prefer implicit over explicit, I also removed all
default settings from CYGCONF_ARGS. But this fully depends on your
point of view.
Since I found no related Cygwin git package repository for guile3.0,
attached a related tar.gz file.
Thanks!
Hannes
[-- Attachment #2: guile3.0-3.0.8-2.src.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 4287 bytes --]
next reply other threads:[~2022-10-04 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 18:06 Hannes Müller [this message]
2022-10-04 23:07 ` Mike Gran
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=0731d827b9d5f2261764808a2ea6617592169883.camel@gmail.com \
--to=h.c.f.mueller@gmail.com \
--cc=cygwin@cygwin.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).