From: Jan Nijtmans <jan.nijtmans@gmail.com>
To: cygwin@cygwin.com
Subject: Re: sqlite3 not being built with libreadline
Date: Sun, 28 Feb 2016 10:47:00 -0000 [thread overview]
Message-ID: <CAO1jNwsP+xFwDoq+zn2z4uYagm4rzuVsy_RXdjQv-pEWyLhhVA@mail.gmail.com> (raw)
In-Reply-To: <56D1F5D1.8030404@cs.umass.edu>
2016-02-27 20:15 GMT+01:00 Eliot Moss:
> linenoise is not configurable while readline is. I doubt the added size
> is much of a big deal with something as large as sqlite is already. The
> linenoise project itself suggests using readline if it's available and
> linenoise if readline is not.
This is a convincing argument for me. I'll provide a new build (3.11.0-2)
next week.
Regards,
Jan Nijtmans
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-02-28 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 8:47 Kenneth Smith
2016-02-27 10:51 ` Jan Nijtmans
2016-02-27 17:19 ` Kenneth Smith
2016-02-27 19:15 ` Eliot Moss
2016-02-28 10:47 ` Jan Nijtmans [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=CAO1jNwsP+xFwDoq+zn2z4uYagm4rzuVsy_RXdjQv-pEWyLhhVA@mail.gmail.com \
--to=jan.nijtmans@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).