From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: vim-8.0.1376-1: Possible bug with ruby extensions
Date: Fri, 09 Feb 2018 18:35:00 -0000 [thread overview]
Message-ID: <52c5d424-a999-78ce-f69b-8c55c17c6ce7@cygwin.com> (raw)
In-Reply-To: <CAKrHFwkqiB9WHC8UF3H1FgNM0s7=AhQ0AjmvMPQ8T9_PeqeB1g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 497 bytes --]
On 2018-02-08 20:51, Ameya Vikram Singh wrote:
> I tried the latest ViM package(vim-8.0.1428-1).
> Even the current version has the same problem.
>
> I do have the **ruby** runtime libraries installed and even the
> development headers package also installed.
Confirmed. The configure script changed how it was detecting the Ruby
shared library in a way which was unportable to non-ELF platforms. A
fix will be included in the next release.
Thanks for reporting,
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2018-02-09 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 16:37 Ameya Vikram Singh
2018-02-06 18:26 ` Brian Inglis
2018-02-09 2:51 ` Ameya Vikram Singh
2018-02-09 18:35 ` Yaakov Selkowitz [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52c5d424-a999-78ce-f69b-8c55c17c6ce7@cygwin.com \
--to=yselkowitz@cygwin.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).