On Thu, Jul 23, 2015 at 10:31:08AM -0500, Bruce Dubbs wrote:
> Armin K. wrote:
> >On 22.07.2015 23:55, Ken Moffat wrote:
> >>[  2%] Generating kbookmarkmerger.1
> >>file:/opt/kf5/share/kf5/kdoctools/customization/dtd/kdex.dtd:102:
> >>warning: failed to load external entity
> >>"file:/opt/kf5/share/kf5/kdoctools/customization/dtd/searched_dir-NOTFOUND/docbookx.dtd"
> >>%DocBookDTD;
> >>             ^
> >>Entity: line 1:
> >>  %DocBookDTD;
> >>              ^
> >>The message in kdelibs4support comes from
> >>cmake/FindDocBookXML4.cmake which seems to be looking for
> >>docbookx.dtd and by default is looking for a 4.2 version (in the
> >>directory name).  Fixed by adding
> >>
> >>  -DDocBookXML_FIND_VERSION=4.5
> >>
> >>when running cmake on kdelibs4support.
> >>
> >
> >I explicitly use a sed for that. Not sure if it was and if not, why not
> >it was merged to the main book when KF5 section was added.
> >
> >But, if that cmake option works, I'd be happy to use that instead of
> >a sed.
> 
> I didn't need either the sed or the -D option.  Perhaps the configuration in
> docbook-xml-4.5 wasn't done.  See the part that starts as
> 
> for DTDVERSION in 4.1.2 4.2 4.3 4.4
> ...
> done
> 

Unless I am misunderstanding those commands, all they are doing is
updating /etc/xml/catalog.  The cmake script looks for a versioned
directory containing docbookx.dtd.  Specifically, a 4.2 versioned
directory.

Certainly, I don't think we have altered those commands in years,
and I originally had to paste them all to get things working.  And
yes, I did review them yesterday, and checked that my catalog
contains a 4.2 conversion.  But the catalog is not being used in
this case.

Do you have a log which shows cmake found it, or does "I didn't need
it" mean that none of the kf5 packages which you built had a problem ?
If the latter, kf5 base-apps is not in either book.

ĸen
-- 
This one goes up to eleven!
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to