Errors in Interprocess doc build

[John Maddock]

While investigating this ticket: ​https://svn.boost.org/trac/boost/ticket/7899#comment:12 I've found a number of errors in the interprocess docs build.

The first is:

interprocess.qbk: warning: Missing [endsect] detected at end of file.

and then:

../../../bin.v2/libs/interprocess/doc/msvc-10.0/debug/auto-index-internal-on/auto-index-verbose-on/auto-index-on/threading-multi/interprocess.auto_index.docbook:15546: element anchor: validity error : ID boost.interprocess.std.vector_type already defined
                                 <anchor id="boost.interprocess.std.vector_type"
                                                                               ^
../../../bin.v2/libs/interprocess/doc/msvc-10.0/debug/auto-index-internal-on/auto-index-verbose-on/auto-index-on/threading-multi/interprocess.auto_index.docbook:15547: element anchor: validity error : ID boost.interprocess.std.char_type already defined
le="identifier">char_type</phrase> <anchor id="boost.interprocess.std.char_type"
                                                                               ^
../../../bin.v2/libs/interprocess/doc/msvc-10.0/debug/auto-index-internal-on/auto-index-verbose-on/auto-index-on/threading-multi/interprocess.auto_index.docbook:15548: element anchor: validity error : ID boost.interprocess.std.int_type already defined
ype</phrase>                        <anchor id="boost.interprocess.std.int_type"

Plus a few more like that.

The first of these is the more worrying, as it can cause quickbook to emit invalid docbook XML (as well as messing up your formatting).

[Ion Gaztañaga]

Thanks John, but I can build documentation locally and there are no changes wrt trunk. The rest of libraries are in version 1.52. I'll try to do the same with after updating my trunk sandbox but I won't have time for this until tomorrow.

[anonymous]

The errors are in SVN Trunk: the doc build does go to completion OK, and the docs do look OK too, but the errors shown mean that the docbook generated isn't strictly valid. I suspect this is one of the things slowing down the doc build, but we won't know for sure until everything is valid Docbook XML.

[Ion Gaztañaga]

This seems fixed in trunk. Could I close the issue?

[John Maddock]

Confirmed.