21 Jul
2004
21 Jul
'04
3:39 p.m.
Michael Glassford wrote:
Jonathan Wakely wrote: ...
Exit status 139 means it's signal 11 (segfault), if that helps.
Thanks. Unfortunately it doesn't help, because every test is failing with that same error and I don't have any way to determine why. My best guess is a configuration problem, such as the appropriate threading library not being installed.
The tests ran successfully for the same toolset in 1.31. A missing library would result in linker errors. Regards, m