libs/config/test/link/Jamfile.v2 confuses process_jam_log

[Dave Abrahams]

[ERROR   ] # running checked system commands in /usr/local/src/boost-bitten/boost/status: ['"/usr/local/src/boost-bitten/tools_regression/build/bin/gcc-4.1.2/release/process_jam_log" "/usr/local/src/boost-bitten/results" <"/usr/local/src/boost-bitten/results/bjam.log"']
[INFO    ] boost_root: /usr/local/src/boost-bitten/boost
[ERROR   ] Traceback (most recent call last):
[INFO    ] locate_root: /usr/local/src/boost-bitten/results
[ERROR   ]   File "/usr/local/src/boost-bitten/run.py", line 52, in <module>
[INFO    ] *****Error - No "boost-test" lines encountered.
[ERROR   ]     runner(root)
[INFO    ]      (Usually occurs when bjam was envoked without the --dump-tests option

Is there a reason that can't be a regular link test? Does it have to be building a library? If the latter, can't we just make that library part of the requirements for a regular link test target?

[John Maddock]

Dave,

That Jamfile tests the auto-linking code: it is very important that the library is not a dependency of the executable, since then we're not testing what we think we are :-(

Obviously this Jamfile only makes any sense for Windows compilers that support auto-linking, hence it's not part of status/Jamfile.v2.

John.

[John Maddock]

Dave, I'm closing this down now, please reopen if it's still an issue.