headers
Rene Rivera | 10 Oct 04:37

Doc build failure... For bjam.

So had some time tonight to read some emails... And The problem I'm 
having with building the bjam docs has nothing to do with what Beman has 
been ahving problems with. When I try and build the bjam docs, note I 
build them in standalone mode, I get the following:

====
xslt-xsltproc 
..\..\..\bin.v2\tools\jam\doc\msvc-9.0xp\dbg\lnk-sttc\thrd-mlt\bjam.docbook
../../../bin.v2/tools/jam/doc/msvc-9.0xp/dbg/lnk-sttc/thrd-mlt/bjam.xml:2: 
warning: failed to load external entity 
"http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"
BoostBook XML V1.0//EN" 
"http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"

         ^
../../../bin.v2/tools/jam/doc/msvc-9.0xp/dbg/lnk-sttc/thrd-mlt/bjam.xml:839: 
parser error : Entity 'nbsp' not defined
         </varlistentry> 
<varlistentry><term><literal>-d&nbsp;<emphasis>n</emphas
                                                              ^
../../../bin.v2/tools/jam/doc/msvc-9.0xp/dbg/lnk-sttc/thrd-mlt/bjam.xml:871: 
parser error : Entity 'nbsp' not defined
         </varlistentry> 
<varlistentry><term><literal>-d&nbsp;+<emphasis>n</empha
                                                              ^
../../../bin.v2/tools/jam/doc/msvc-9.0xp/dbg/lnk-sttc/thrd-mlt/bjam.xml:877: 
parser error : Entity 'nbsp' not defined
         </varlistentry> 
<varlistentry><term><literal>-d&nbsp;0</literal></term>
                                                              ^
(Continue reading)

Permalink | Reply |
headers
Eric Niebler | 10 Oct 05:26

Re: Doc build failure... For bjam.


Rene Rivera wrote:
> So had some time tonight to read some emails... And The problem I'm 
> having with building the bjam docs has nothing to do with what Beman has 
> been ahving problems with. When I try and build the bjam docs, note I 
> build them in standalone mode, I get the following:
> 
> ====
> xslt-xsltproc 
> ..\..\..\bin.v2\tools\jam\doc\msvc-9.0xp\dbg\lnk-sttc\thrd-mlt\bjam.docbook
> ../../../bin.v2/tools/jam/doc/msvc-9.0xp/dbg/lnk-sttc/thrd-mlt/bjam.xml:2: 
> warning: failed to load external entity 
> "http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"
> BoostBook XML V1.0//EN" 
> "http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"

Looks like either you've configured the boostbook toolset wrong in your 
user-config.jam (bad paths?) or else xsltproc is not finding the catalog 
file. Are you running this under cygwin, by any chance?

--

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com
Permalink | Reply |
headers
Daniel James | 10 Oct 10:01
Favicon

Re: Doc build failure... For bjam.

2008/10/10 Rene Rivera <grafikrobot <at> gmail.com>:
>
> So why am I getting these errors? Probably because I'm using the
> docbook-xml-4.5 and docbook-xsl-1.74.0 releases instead of the extremely old
> 4.2 and wahtever else the xsl one is. But using the latest docbook-xml-4.x
> plus the latest docbook-xsl-1.x.y used to work.

Using the latest xsl files should be okay (I'm using 1.73.2, the
current one in the Ubuntu beta), but the bookbook dtd imports the 4.2
docbook dtd so I think you have to use docbook-xml-4.2.

2008/10/10 Eric Niebler <eric <at> boost-consulting.com>:
>
> Looks like either you've configured the boostbook toolset wrong in your
> user-config.jam (bad paths?) or else xsltproc is not finding the catalog
> file. Are you running this under cygwin, by any chance?

You (Rene) might need to delete bin.v2/boostbook.jam. It doesn't
always get updated when the configuration is changed.

It doesn't look like you're using cygwin, which is a pity as cygwin's
easier to setup. There are a few dodgy version of xsltproc for
windows. If you have further problems you might want to look at the
rough instructions at:

http://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted#Windows

I successfully used the setup I described (apart from a couple of
problems which won't affect the jam documentation). Feel free to make
changes.
(Continue reading)

Permalink | Reply |
headers
Rene Rivera | 11 Oct 18:48

Re: Doc build failure... For bjam.

Daniel James wrote:
> 2008/10/10 Rene Rivera <grafikrobot <at> gmail.com>:
>> So why am I getting these errors? Probably because I'm using the
>> docbook-xml-4.5 and docbook-xsl-1.74.0 releases instead of the extremely old
>> 4.2 and wahtever else the xsl one is. But using the latest docbook-xml-4.x
>> plus the latest docbook-xsl-1.x.y used to work.
> 
> Using the latest xsl files should be okay (I'm using 1.73.2, the
> current one in the Ubuntu beta), but the bookbook dtd imports the 4.2
> docbook dtd so I think you have to use docbook-xml-4.2.

It's worked before for me with docbook-xml > 4.2.

> 2008/10/10 Eric Niebler <eric <at> boost-consulting.com>:
>> Looks like either you've configured the boostbook toolset wrong in your
>> user-config.jam (bad paths?) or else xsltproc is not finding the catalog
>> file. Are you running this under cygwin, by any chance?
> 
> You (Rene) might need to delete bin.v2/boostbook.jam. It doesn't
> always get updated when the configuration is changed.

I always start clean by deleting all of bin.v2. But for my configuration 
there is no bin.v2/boostbook.jam.

> It doesn't look like you're using cygwin, which is a pity as cygwin's
> easier to setup.

I have no problems setting up the win32 versions, and I suspect I'd have 
the same problems in cygwin.
(Continue reading)

Permalink | Reply |
headers
Daniel James | 12 Oct 12:12
Favicon

Re: Doc build failure... For bjam.

2008/10/11 Rene Rivera <grafikrobot <at> gmail.com>:
>
> It's worked before for me with docbook-xml > 4.2.

I get validity errors for later versions. As far as I know, there's no
real advantage to using later versions. And since there is very little
development time spent on boostbook, the less changing factors the
better.

Daniel
Permalink | Reply |
headers
Rene Rivera | 11 Oct 18:40

Re: Doc build failure... For bjam.

Did I mention that the doc build was working? As it's how I did the 
3.1.16 bjam release long ago now.

Eric Niebler wrote:
> 
> Rene Rivera wrote:
>> So had some time tonight to read some emails... And The problem I'm 
>> having with building the bjam docs has nothing to do with what Beman 
>> has been ahving problems with. When I try and build the bjam docs, 
>> note I build them in standalone mode, I get the following:
>>
>> ====
>> xslt-xsltproc 
>> ..\..\..\bin.v2\tools\jam\doc\msvc-9.0xp\dbg\lnk-sttc\thrd-mlt\bjam.docbook 
>>
>> ../../../bin.v2/tools/jam/doc/msvc-9.0xp/dbg/lnk-sttc/thrd-mlt/bjam.xml:2: 
>> warning: failed to load external entity 
>> "http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"
>> BoostBook XML V1.0//EN" 
>> "http://www.boost.org/tools/boostbook/dtd/boostbook.dtd"
> 
> 
> Looks like either you've configured the boostbook toolset wrong in your 
> user-config.jam (bad paths?)

My user-config.jam has:

using python : 2.5 ;
using docutils : C:/Boost/share/docutils ;
using doxygen ;
(Continue reading)

Permalink | Reply |
headers
Steven Watanabe | 11 Oct 19:21

Re: Doc build failure... For bjam.

AMDG

Rene Rivera wrote:
> <?xml version="1.0"?>
> <!DOCTYPE catalog
>   PUBLIC "-//OASIS/DTD Entity Resolution XML Catalog V1.0//EN"
>   "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
>   <rewriteURI 
> uriStartString="http://www.boost.org/tools/boostbook/dtd/" 
> rewritePrefix="file:///Boost/share/boostbook/dtd/"/>
>   <rewriteURI 
> uriStartString="http://docbook.sourceforge.net/release/xsl/current/" 
> rewritePrefix="file:///Boost/share/docbook-xsl-1.74.0/"/>
>   <rewriteURI 
> uriStartString="http://www.oasis-open.org/docbook/xml/4.2/" 
> rewritePrefix="file:///Boost/share/docbook-xml-4.5/"/>
> </catalog>

Does it work if you change file:///Boost/share... to include the drive?

In Christ,
Steven Watanabe
Permalink | Reply |
headers
Rene Rivera | 11 Oct 21:05

Re: Doc build failure... For bjam.

Steven Watanabe wrote:
> Rene Rivera wrote:
>>   <rewriteURI 
>> uriStartString="http://docbook.sourceforge.net/release/xsl/current/" 
>> rewritePrefix="file:///Boost/share/docbook-xsl-1.74.0/"/>
>>   <rewriteURI 
>> uriStartString="http://www.oasis-open.org/docbook/xml/4.2/" 
>> rewritePrefix="file:///Boost/share/docbook-xml-4.5/"/>
> 
> Does it work if you change file:///Boost/share... to include the drive?

Thank you for suggesting that!
<http://svn.boost.org/trac/boost/changeset/49287>

--

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
Permalink | Reply |
headers
Daniel James | 12 Oct 12:16
Favicon

Re: Doc build failure... For bjam.

2008/10/11 Rene Rivera <grafikrobot <at> gmail.com>:
>
> Thank you for suggesting that!
> <http://svn.boost.org/trac/boost/changeset/49287>

I'm glad you've got it working. It looks like we really need someone
to take responsibility for maintaining the windows boostbook build
tools or future problems will only be caught during the bjam release
process.

Daniel
Permalink | Reply |
headers
Beman Dawes | 13 Oct 17:04
Favicon

Re: Doc build failure... For bjam.

Daniel James wrote:
> 2008/10/11 Rene Rivera <grafikrobot <at> gmail.com>:
>> Thank you for suggesting that!
>> <http://svn.boost.org/trac/boost/changeset/49287>
> 
> I'm glad you've got it working. It looks like we really need someone
> to take responsibility for maintaining the windows boostbook build
> tools or future problems will only be caught during the bjam release
> process.

Agreed. Who is the logical person to take responsibility?

--Beman
Permalink | Reply |
headers
Daniel James | 13 Oct 20:19
Favicon

Re: Doc build failure... For bjam.

2008/10/13 Beman Dawes <bdawes <at> acm.org>:
> Daniel James wrote:
>>
>> It looks like we really need someone
>> to take responsibility for maintaining the windows boostbook build
>> tools or future problems will only be caught during the bjam release
>> process.
>
> Agreed. Who is the logical person to take responsibility?

I don't know. I can't as I don't always have a windows machine.
Permalink | Reply |
headers
John Maddock | 16 Oct 11:22

Re: Doc build failure... For bjam.

Beman Dawes wrote:
>> Daniel James wrote:
>>> 2008/10/11 Rene Rivera <grafikrobot <at> gmail.com>:
>>>> Thank you for suggesting that!
>>>> <http://svn.boost.org/trac/boost/changeset/49287>
>>>
>>> I'm glad you've got it working. It looks like we really need someone
>>> to take responsibility for maintaining the windows boostbook build
>>> tools or future problems will only be caught during the bjam release
>>> process.
>>
>> Agreed. Who is the logical person to take responsibility?

I have a working Win32 setup as well, as for maintaining it that's harder: 
not least because it's hard to tell when it's broken!  The doxygen 
integration seems to be particulary flaky: often reporting success when it 
in fact failed, or at least mangled the output :-(

John.
Permalink | Reply |

Gmane