> Date: Wed, 10 Aug 2016 18:39:05 +0100 > From: Ken Moffat <[email protected]> > Subject: [blfs-dev] PAM now fails to build docs with links > > I've been adding PAM to my desktop builds for a while. By the time > I get to that point I've already built links, docbook, xslt. > > Until now that has built without problems, although it has not > built the docs (I don't have w3m), so e.g. a couple of months ago I > got > /usr/share/doc/Linux-PAM-1.2.1 > /usr/share/doc/Linux-PAM-1.2.1/draft-morgan-pam-current.txt > /usr/share/doc/Linux-PAM-1.2.1/index.html > /usr/share/doc/Linux-PAM-1.2.1/rfc86.0.txt > > That was with Linux-PAM-1.2.1 and links-2.12. > > Today, with 1.3.0 and 2.13 it tries to build the docs, and fails: > > /usr/bin/xsltproc --stringparam generate.toc "book toc" \ > --stringparam section.autolabel 1 \ > --stringparam section.label.includes.component.label 1 \ > --stringparam toc.max.depth 2 --xinclude --nonet \ > http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl > Linux-PAM_SAG.xml | /usr/bin/links -no-numbering -no-references -dump > > Linux-PAM_SAG.txt > Unknown option -no-numbering
Hmmm, those '/usr/bin/links ...' args don't look like the 'real' 'links' prog: looks a bit more like the ~similar 'elinks' - ref e.g.: http://elinks.or.cz/documentation/manpages/elinks.1.html Maybe the relevant pam-devs have got elinks dropped-in for 'links'? > > The work-around is to add '--disable-regenerate-docu' : that gives > the same docs as before (and the index.html is useless with out the > guides it links to). > > Should I add that as an optional switch for people who have the > docbook deps and xslt but not w3m ? > If they're using links/elinks to generate docs, then why 'require' w3m to build the docs. akh -- -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
