Daniel Baumann wrote:
how about making the number of threads configurable, so that we can use a lower number on sparc?
Do you mean making the number of threads configurable in the test (make check)? Sure, if the failure is caused by too many threads in the test I'll happily reduce them.
But as 16 threads is a small number for what plzip can manage, I would like to be sure that the number of threads is indeed the problem. Could you, please, edit line 77 of plzip-0.7/testsuite/check.sh to remove all numbers larger than 10 and see if plzip passes the test then?
Given that the failure message shown in the build log is "Aborted", it could be produced by a lack of enough memory. (16 threads use more than 80MiB).
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
