22 Jul
2004
22 Jul
'04
1:45 p.m.
Martin Wille wrote:
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.
I was thinking of Windows, where you can link against a .lib file but must have the corresponding .dll file available at runtime. This isn't the case with Linux? Mike