Clisp 2.49 fails to build with upgrade to readline 7.0

[bdubbs@…]

From blfs-dev:

Eujean Snyman <freddie13.ff@gmail.com>

The simplest fix I could find:

--- modules/readline/readline.lisp.orig
+++ modules/readline/readline.lisp
@@ -424,7 +424,7 @@ name in ~/.inputrc.
"The version of this incarnation of the readline library, e.g., 0x0402."))
(def-c-var gnu-readline-p (:name "rl_gnu_readline_p") (:type int)
(:documentation "True if this is real GNU readline."))
-(def-c-var readline-state (:name "rl_readline_state") (:type int)
+(def-c-var readline-state (:name "rl_readline_state") (:type ulong)
(:documentation "Flags word encapsulating the current readline state."))
(def-c-var editing-mode (:name "rl_editing_mode") (:type int)
(:documentation "Says which editing mode readline is currently using.

Looks like a candidate for a sed.

sed -i /readline-state/s/int/ulong/ modules/readline/readline.lisp

Not tested.

[ken@…]

I can replicate the problem, but only when libffcall has been installed [static libs only :-( ] and the configure arguments use --libffcall-prefix=/usr (or wherever it was installed).

In such a case, the build fails as described. Adding the patch from upstream allows it to complete, and the information from 'clisp --version' will then also include /usr/lib/libavcall.a /usr/lib/libcallback.a in the gcc details, followed by libffcall 1.13 at the end of the libraries and READLINE at the start of the Features.

I'll add the patch as optional with a note it is required only if libffcall is being used.

[ken@…]

Fixed, with additional explanations, at r18942.

[ken@…]

r18942 fixed at r18944.