"Oskar Liljeblad" <[EMAIL PROTECTED]> writes: > On Thursday, August 11, 2005 at 23:14, Simon Josefsson wrote: >> >> > I don't know if the readline module covers this, but on recent >> > Fedora/RedHat systems you'll need to link with ncurses or some >> > other library providing certain termcap (or was it terminfo?) >> > functions... You don't need to do this with Debian. >> >> This appears to be the case, I have access to one such system, so I >> can try M4 magic on it. I have no idea how to solve this without a >> lot of code though (i.e., if AC_TRY_LINK fail, try the exact same >> AC_TRY_LINK again but with -ltermcap in LIBS too). Relevant current >> code below. >> >> Thoughts? > > I'll check the code soon, but why don't you use READLINE_LIBS instead > of LIBREADLINE etc? That's the convention most other automake macros > I've seen use. Oh well, I guess it's just my personal taste :)
There are several uses of LIB* and LTLIB* in gnulib, although from a cursory glance all appear to stem from gettext. > Also check this: > > http://ac-archive.sourceforge.net/Installed_Packages/vl_lib_readline.html > > It also mentions libedit and libeditline (apparently those are other > GNU readline-like implementations). That seem like a quite useful macro, and it solve the termcap problem by having two nested for loops. Nice. And I hadn't realized edit/editline also provided the readline API. I'll try to work on incorporating those ideas in this macro. Thanks. _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
