AMDG On 02/07/2014 02:10 AM, John Maddock wrote:
I don't think that is the issue - it's not that the output is truncated - it's that there is *no output at all*. Or rather that the link for the "failure" leads to a file which did actually compile correctly.
The basic problem is that process_jam_log assumes one test case or one library = one source file. Support for incremental builds makes this a silent error. We want to ignore the old output when the target is updated. Thus, when process_jam_log handles a compile.c++ target, it discards any previous output for the same lib target. Unfortunately, this includes output produced when compiling another source file. The result is that the last source file processed is the only one that appears in the report. I looked into fixing this a while back, but it's non-trivial. In Christ, Steven Watanabe