I don't understand it either. I was told that some systems required it so I put it in. It did not break on any of the systems that we test on, so I assumed that it was a good patch.
On 3/31/17, Lonnie Abelbeck <lon...@abelbeck.com> wrote: > Hi, > > This commit: [bf28a55d] > http://www.sqlite.org/src/fdiff?v1=cacf2616abf6e4a5&v2=2893b823ecc86cea&sbs=0 > > Keeps libedit from be found and used. > > Using SQLite 3.18.0: --enable-editline --disable-readline > -- > checking editline/readline.h usability... yes > checking editline/readline.h presence... yes > checking for editline/readline.h... yes > checking for library containing readline... no > -- > and no libedit support in /usr/bin/sqlite3 > > Reverting [bf28a55d] > -- > checking editline/readline.h usability... yes > checking editline/readline.h presence... yes > checking for editline/readline.h... yes > checking for library containing readline... -ledit > -- > and libedit support is working again in /usr/bin/sqlite3 > > I don't understand why the libtinfo requirement was added for libedit. > > Lonnie > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
