LinuxQuestions.org - [SOLVED] readline 6 for slackware-current needed (nftables)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - readline 6 for slackware-current needed (nftables) (https://www.linuxquestions.org/questions/slackware-14/readline-6-for-slackware-current-needed-nftables-4175492242/)

readline 6 for slackware-current needed (nftables)

Hello,
I would like to try nftables with slackware-current. It needs recent readline from 6.X version.
Where could I ask to include it parraler with readline 5.X into slackware-current?
Do I need to do it myself or maybe there are plans to include it in slackware current in near future?

Hi.

Your issue has to do with how nftables checks for and links libreadline and how Slackware is configured.

I've prepared a patch you should apply to nftables before running autogen.sh. This should solve your problem.

--mancha

PS As clarification for others who end up in this thread, OP's problem is not due to Slackware's readline version.

I found the solution to use readline-5.2 on Slackware with nftables. I need to add LIBS=”-ltermcap -lgmp” to ./configure step
thanks for reply.

Glad you solved it though I think my patch solution is more organic.

Also, nftables has a hardcoded XML schema path that needs changing if one wants to build the PDF documentation on Slackware:

Code:

--- a/doc/nftables.xml

+++ b/doc/nftables.xml

@@ -1,6 +1,6 @@

 <?xml version="1.0" encoding="UTF-8" ?>

 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"

- "/usr/share/xml/docbook/schema/dtd/4.5/docbookx.dtd">

+ "/usr/share/xml/docbook/xml-dtd-4.5/docbookx.dtd">

 

 <refentry>

        <refentryinfo>

Slackware uses LFS path conventions for docbook as does Arch Linux. Debian, OpenSUSE, and others use the path nftables used.

If drmozes happens on this thread maybe he can shed some light on these differing conventions and how hard-coding issues can be avoided.

--mancha