Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Aug 2011 01:35:04 -0400
From:      "b. f." <>
To:        Daryl Sayers <>,
Subject:   Re: port build breaks at xmlto
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
On Fri, Aug 12, 2011 at 01:18:07PM +1000, Daryl Sayers wrote:
> FreeBSD 7.4
> I am having trouble building the xmlto port on FreeBSD 7.4. I am getting an
> error:
> ===>  Building for xmlto-0.0.24
> make  all-am
> for xml in xmlif.xml xmlto.xml; do  FORMAT_DIR=./format  /usr/local/bin/bash ./xmlto -o man/man1 man ./doc/$xml ;  done || ( RC=$?; exit $RC )
> xmlto: /usr/ports/textproc/xmlto/work/xmlto-0.0.24/./doc/xmlif.xml does not validate (status 3)
> xmlto: Fix document syntax or use --skip-validation option
> I/O error : Attempt to load network entity
> /usr/ports/textproc/xmlto/work/xmlto-0.0.24/./doc/xmlif.xml:4: warning: failed to load external entity ""
>    "">;
> ....

xmlto should be using /usr/local/share/xml/docbook/4.2/docbookx.dtd,
which should be installed by the build dependency
textproc/docbook-xml, but instead is trying to fetch this file from a
remote location, and failing.  Check to see if this file is present,
and intact.  If it isn't, then reinstall textproc/docbook-xml. You
could look at the file (and compare it to the reference file from the
remote location), and the output of "pkg_info -ag", to see if anything
is corrupted.

> After alot of frustration I decided to throw everything away and start again:
> # pkg_delete -a

Okay, you've instructed the system to delete the registered files and
directories in the step above -- but is any garbage left in /usr/local
afterward?  After the above step, you should check to see that
/usr/local only contains files that you have placed there, and that
won't interfere with new port installations.

> # cd /usr/ports; rm -fr *
> # csup -h /usr/share/examples/cvsup/ports-supfile
> # cd /usr/ports/textproc/xmlto
> # make

Usually, it's a good idea to perform "make deinstall-all clean all"
(in that order), although in this case it should not have made a
difference for the first build, if you had succeeded in cleaning
/usr/local and /usr/ports.

> Using the defaults when the config screens appear. As there are now no packages
> installed and the ports tree is brand new there should be no problems but in
> the end it still fails with the same message. My /etc/make.conf is empty also.
> Why cant I build this package.

This port was built on July 17 on the build cluster with 7.3-RELEASE-p4:

so while there may be a bug in the port, or in one of its
dependencies, it is more probable that your build is polluted.  If you
don't want to use a binary package downloaded from the server, then
you'll have to be patient, and break down the build until you find the
precise location where it is failing, even though that is a nuisance.
A complete build transcript and config.log would help.


Want to link to this message? Use this URL: <>