When building debian package from master, I noticed this kind of error message:
s ../../../doc/stylesheets/serdoc2man.xsl auth.xml make[3]: s: Command not found ../../Makefile.modules:283: recipe for target 'auth.7' failed
The line in Makefile.modules is here:
$(MOD_NAME).7: $(MOD_NAME).xml $(DOCBOOK) -s ../../../doc/stylesheets/serdoc2man.xsl $<
Could it be that variable $(DOCBOOK) has not been defined?
-- Juha
Grepping for that variable in the makefiles reveals that it looks for docbook2x-man or db2x_docbook2man.
Likely not available in your system, so either they were part of a installed package or related dependency in the past, or just a new package that needs to be added as build dependency.
Cheers, Daniel
On 20.08.18 10:26, Juha Heinanen wrote:
When building debian package from master, I noticed this kind of error message:
s ../../../doc/stylesheets/serdoc2man.xsl auth.xml make[3]: s: Command not found ../../Makefile.modules:283: recipe for target 'auth.7' failed
The line in Makefile.modules is here:
$(MOD_NAME).7: $(MOD_NAME).xml $(DOCBOOK) -s ../../../doc/stylesheets/serdoc2man.xsl $<
Could it be that variable $(DOCBOOK) has not been defined?
-- Juha
Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Daniel-Constantin Mierla writes:
Grepping for that variable in the makefiles reveals that it looks for docbook2x-man or db2x_docbook2man.
Likely not available in your system, so either they were part of a installed package or related dependency in the past, or just a new package that needs to be added as build dependency.
In debian stretch, /usr/bin/docbook2x-man is in package docbook2x and that package is NOT listed as build dependency in pkg/kamailio/deb/stretch/control.
I added that package and the error was gone, but a new ones were produced:
/usr/bin/docbook2x-man -s ../../../doc/stylesheets/serdoc2man.xsl auth.xml auth.xml:7: warning: failed to load external entity "../../../../doc/docbook/entities.xml" %docentities; ^ Entity: line 1: %docentities; ^ auth.xml:25: parser error : Entity 'kamailio' not defined The <command>auth</command> module of &kamailio; provides basic functional ^ auth.xml:208: parser error : Entity 'kamailio' not defined can be divided into several partitions. Each &kamailio; process is assig ^ auth.xml:213: parser error : Entity 'kamailio' not defined conditions. In the worst case, when only one &kamailio; process receive ^ auth.xml:532: parser error : Entity 'kamailio' not defined separated by a comma. For challenges generated by &kamailio;, this ^ auth.xml:535: parser error : Entity 'kamailio' not defined parameter will be present in challenges created by &kamailio;. This may ^ auth.xml:537: parser error : Entity 'kamailio' not defined make your &kamailio; not comply with RFC 3261. ^ -- Juha
Juha Heinanen writes:
I added that package and the error was gone, but a new ones were produced:
/usr/bin/docbook2x-man -s ../../../doc/stylesheets/serdoc2man.xsl auth.xml auth.xml:7: warning: failed to load external entity "../../../../doc/docbook/entities.xml"
Digging more to this, there is two auth.xml files in modules/auth: one in auth dir and another in auth/doc dir. Looks like the former (that includes the above failing entity) should be removed.
-- Juha
Am Dienstag, 21. August 2018, 15:15:15 CET schrieb Juha Heinanen:
I added that package and the error was gone, but a new ones were produced:
/usr/bin/docbook2x-man -s ../../../doc/stylesheets/serdoc2man.xsl auth.xml auth.xml:7: warning: failed to load external entity "../../../../doc/docbook/entities.xml"
Digging more to this, there is two auth.xml files in modules/auth: one in auth dir and another in auth/doc dir. Looks like the former (that includes the above failing entity) should be removed.
Hello Juha,
I checked as well, there are some modules that have a second xml file in the module directory. I looked into the avp and auth modules, it seems that this is for dedicated man pages for this modules, probably coming from the SER times. Coming from Kamailio I think some modules just use the module readme as man page source.
Best regards,
Henning