Boost logo

Boost :

From: Daniel James (daniel_james_at_[hidden])
Date: 2008-06-22 18:59:57


Hi,

I'm getting errors building the combined documentation on Ubuntu
Hardy. The problem seems to be caused by the accumulator library (or
maybe the boost build tools that it uses) using absolute directories
for its build destination, while most other libraries use relative
ones.

Looking through the build output the first error is:

common.copy ../libs/accumulators/doc/tagfile.xml
MkDir1 /home/daniel/boost/branches/release/bin.v2
mkdir: cannot create directory
`/home/daniel/boost/branches/release/bin.v2': File exists

    mkdir "/home/daniel/boost/branches/release/bin.v2"

...failed MkDir1 /home/daniel/boost/branches/release/bin.v2...
...skipped /home/daniel/boost/branches/release/bin.v2/libs for lack of
/home/daniel/boost/branches/release/bin.v2...
...skipped /home/daniel/boost/branches/release/bin.v2/libs/accumulators
for lack of /home/daniel/boost/branches/release/bin.v2/libs...
...skipped /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc
for lack of /home/daniel/boost/branches/release/bin.v2/libs/accumulators...
...skipped /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html
for lack of /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc...
doxygen-action ../bin.v2/libs/accumulators/doc/gcc-4.3/debug/statsdoc.html-dir
Notice: Output directory
`/home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html'
does not exist. I have created it for you.

'../bin.v2' has been previously created as a relative directory, and
here is an absolute directory
'/home/daniel/boost/branches/release/bin.v2', which I think causes
boost build to try to create the same directory twice.

You can see from the output that the required directory gets created
soon after, but boost build seems to remember the error, because later
in the output:

...skipped <p/home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html>statsdoc.html
for lack of /home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html...
...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoclatex.tag
for lack of <p/home/daniel/boost/branches/release/bin.v2/libs/accumulators/doc/html>statsdoc.html...
...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxyfile
for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoclatex.tag...
...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.xml-dir
for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxyfile...
...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxygen
for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.xml-dir...
...skipped <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.boostbook
for lack of <p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.doxygen...
...skipped <p../libs/accumulators/doc>statsdoc.xml for lack of
<p../bin.v2/libs/accumulators/doc/gcc-4.3/debug>statsdoc-xml.boostbook...

Which then causes more targets to be skipped later on, preventing the
documentation from being built.

It seems that if bjam is then run again the problem doesn't occur,
probably because the problem directories are already created. I'm
running it at the moment and it looks like it'll probably succeed (it
takes a while).

I can send the complete build output if it'll help.

thanks,

Daniel


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk