From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: Kawa mailing list <kawa@sourceware.org>
Subject: SLIB (full/general) in Kawa?
Date: Fri, 01 Jan 2021 13:50:07 -0500 [thread overview]
Message-ID: <31129.1609527007@localhost> (raw)
Does anyone have any suggestions for getting SLIB working in Kawa?
I mean the full/general SLIB distribution, not only the few parts that
are already in Kawa. When I try to include SLIB's kawa.init file, I get
errors that seem related to the use of colons in SLIB identifiers. In
particular, I thought I'd check if someone had SLIB running before
getting in too deep. (I'm also not sure if it is possible to "escape" a
colon to at least enable a very hackish "search and replace" kind of
workaround by modifying a local copy of the SLIB sources.)
I found an old thread/bug-report in the old Savannah repository:
http://savannah.gnu.org/bugs/?19263
but nothing specific in the current Gitlab repository and in general am
unsure of the current state of things on this front.
I'll also take the occasion to say a heartfelt thanks and best wishes
for the new year to all of the Kawa community.
Regards,
-chaw
next reply other threads:[~2021-01-01 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 18:50 Sudarshan S Chawathe [this message]
2021-01-01 19:25 ` Per Bothner
2021-01-01 21:03 ` Sudarshan S Chawathe
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=31129.1609527007@localhost \
--to=chaw@eip10.org \
--cc=kawa@sourceware.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).