Boost logo

Boost-Build :

From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2006-10-07 12:46:46


I've noticed some inconsistent behavior with the build system that I
want to show you. Our nightly regression builds some 30+
applications from some 100+ libraries and most nights a couple of
source files fails to produce an object file even though there's no
error message indicating problems. Note that we're writing to a
local disk (not NFS mounted) although we do read from NFS. From our
build log, we've found that bjam queues up a source file to compile
it, but there is no error message in the log file and no object file
is produced.

For example, from our Linux debug shared library build,


failed to produce an object file or an error message but all the
other files sandwiched around them build fine.

gcc.compile.c++ presto/votd/gcc-3.4.3/debug/Apst_KinBC_Velocity.o
gcc.compile.c++ presto/votd/gcc-3.4.3/debug/Apst_Kinematics_Init.o
gcc.compile.c++ presto/votd/gcc-3.4.3/debug/Apst_Lanczos.o
gcc.compile.c++ presto/votd/gcc-3.4.3/debug/Apst_Lanczos_Parser.o
gcc.compile.c++ presto/votd/gcc-3.4.3/debug/Apst_LineWeld.o
gcc.compile.c++ presto/votd/gcc-3.4.3/debug/Apst_LineWeld_Parser.o
gcc.compile.c++ presto/votd/gcc-3.4.3/debug/Apst_MassProperties.o

and the shared library fails to link presto/votd/gcc-3.4.3/debug/
g++: presto/votd/gcc-3.4.3/debug/Apst_Lanczos_Parser.o: No such file
or directory
g++: presto/votd/gcc-3.4.3/debug/Apst_LineWeld.o: No such file or

Note that if I just reissue the build command, these two files
compile fine, the library links and the executables link without
problem. I can envision build system and disk failures. We've
scanned the disk we're writing to and found no problems. The problem
surfaces randomly, some nights there's no failures with any toolset,
other nights, small numbers of files (1-5) fail for an irreproducible

Any ideas?

-- Noel Belcourt

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at