[GRASS-user] ./configure oddities

[Glynn Clements]

Zenon Panoussis wrote:

> Likewise,
> 
> checking whether to use Readline... yes
> checking for location of Readline includes...
> checking for readline/readline.h... yes
> checking for readline/history.h... yes
> checking for location of Readline library...
> checking for readline in -lreadline... no
> configure: error: *** Unable to locate Readline library.
> 
> but
> 
> # rpm -ql readline-devel
> /usr/include/readline
> /usr/include/readline/chardefs.h
> /usr/include/readline/history.h
> /usr/include/readline/keymaps.h
> /usr/include/readline/readline.h
> /usr/include/readline/rlconf.h
> /usr/include/readline/rlstdc.h
> /usr/include/readline/rltypedefs.h
> /usr/include/readline/tilde.h
> /usr/lib64/libhistory.a
> /usr/lib64/libhistory.so
> /usr/lib64/libreadline.a
> /usr/lib64/libreadline.so
> 
> It's libreadline it should be looking for instead of readline,
> isn't it?

The test is correct. Readline failures normally indicate that
libreadline is missing depedency information. The library requires
certain termcap functions (tgetent etc), but doesn't list the relevant
library as a dependency.

The configure script can't determine the dependency, because there are
often multiple plausible candidates (libtermcap, libtinfo,
lib[n]curses), and it isn't possible to determine which one is correct
at compile time.

Either build libreadline with correct dependency information, or don't
use --with-readline. The switch only affects whether r.mapcalc uses
readline for interactive input, so it isn't particularly important.

-- 
Glynn Clements <glynn at gclements.plus.com>