Re: [Boost-docs] Xpressive problems

Subject: Re: [Boost-docs] Xpressive problems
From: Beman Dawes (bdawes_at_[hidden])
Date: 2008-12-05 16:30:59

On Fri, Dec 5, 2008 at 10:51 AM, John Maddock <john_at_[hidden]> wrote:
> Beman Dawes wrote:
>>> Looking at the attached bjam log from this morning's trunk doc build,
>>> down at the end, there seem to be a lot of error messages related to
>>> xpressive.
> Beman, there are many errors in there, almost all of which I suspect are
> related to the use of cygwin:
>>> xslt-xsltproc ../bin.v2/libs/asio/doc/gcc-3.4.4/debug/asio_doc.docbook
>>> /bin/sh: line 2: export: `XML_CATALOG_FILES': not a valid identifier
> Probably this relates to \r\n conventions and /bin/sh not being able to
> parse the content that BBv2 produces.
>>> ../bin.v2/libs/asio/doc/gcc-3.4.4/debug/asio_doc.xml:2: warning: failed
>>> to load external entity
>>> >>""
>>> BoostBook XML V1.0//EN"
>>> ""
> Looks like your
> using docbook
> statement has incorrect paths (or paths that cygwin xsltproc can't handle).

My user-config.jam has no "using docbook". There is no mention of such
a using in

Is one needed? If so, what does it look like? Also, there should be an
explicit error message if anything is missing from user-config.jam
that says what is missing and how to correct the problem.

>>> /bin/sh: line 1: gs: command not found
>>> gs -version > gs.version
>>> ...failed Jamfile</cygdrive/c/boost/trunk/libs/accumulators/doc>.check-gs
>>> ../bin.v2/libs/accumulators/doc/gcc-3.4.4/debug/gs.check...
> Looks like you don't have the cygwin version of ghostscript installed
> (ghostscript as well as LaTex are required by accumulators docs).

The cygwin installer says ghostscript is installed, and I can see gs
and related files in bin, so I don't think that's a problem.

> Beman, I'll look into starting a test case, but I honestly think you're
> wasting your time using cygwin. I'd much rather see you using all win32
> builds of bjam/xsltproc/doxygen etc.

The recommendation in is to
use cygwin. Daniel pressed me to use cygwin back when I was using
win32 versions of some of the tools, and indeed problems were reduced
when I switched to cygwin. Given the long length of the tool chain, I
really don't want to have to manually search for and install, and keep
up to date win32 versions.


This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:40 UTC