sorry for bothering you again, but why there's both libs/config/test/Jamfile, and some config-related enties in status/Jamfile (as of CVS HEAD today).
That's yet another thing that can potentially get out of sync. Or there's some good reason for duplication, like you not wanting to run those auto-generated tests as part of main regression suite?
There's too many of them, and they're mainly useful for porting a new compiler to Boost - the shortened tests in status/ are sufficient for normal regression testing. Also some of the individual config tests require a number one human eyeball to decide whether a failure is "real" or "not worth worying about": the latter can occur when there's more than one non-standard feature that could be enabled to achieve the same effect. John.