Thanks Vladimir
I pulled down the example and built it.
Because 64 is explicit, it doesn't get built unless I specify 64 on the command line right? Has 64.cpp got anything to do with the configuration check?
Even if I fix the compilation of it, when I build I get the following:
$ bjam
Performing configuration checks
- 64-bit : no (cached)
If I force the build:
$ bjam -a
Performing configuration checks
- 64-bit : no (cached)
...found 17 targets...
...updating 4 targets...
gcc.compile.c++ app/bin/gcc-4.8/debug/app.o
gcc.compile.c++ util/foo/bin/gcc-4.8/debug/bar.o
gcc.link.dll util/foo/bin/gcc-4.8/debug/libbar.so
gcc.link app/bin/gcc-4.8/debug/app
...updated 4 targets...