I can reproduce this oddity, the workaround is to use --config=force.
Also, I am not sure if it is possible to build with boost=0 at all since it fails. (may be a different bug).
I can reproduce this oddity, the workaround is to use --config=force.
Also, I am not sure if it is possible to build with boost=0 at all since it fails. (may be a different bug).