One of the tests fail in make check when building on ARM http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1755923 Output: FAIL: test_embed_record ============================================================================ Testsuite summary for yaz 4.2.56 ============================================================================ # TOTAL: 42 # PASS: 41 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 ============================================================================ See test/test-suite.log Please report to yaz-help ============================================================================ Let me know if you need any more information.
The test fails also on ppc and s390, so likely it's related to the char type being unsigned by default on arm, ppc and s390. Build with -fsigned-char appended to CFLAGS makes the test suite to pass successfully. I've reported the issue to upstream.
(In reply to comment #1) > The test fails also on ppc and s390, so likely it's related to the char type > being unsigned by default on arm, ppc and s390. Build with -fsigned-char > appended to CFLAGS makes the test suite to pass successfully. I've reported > the issue to upstream. Thanks, got a link to upstream report?
(In reply to comment #2) > (In reply to comment #1) > > The test fails also on ppc and s390, so likely it's related to the char type > > being unsigned by default on arm, ppc and s390. Build with -fsigned-char > > appended to CFLAGS makes the test suite to pass successfully. I've reported > > the issue to upstream. > > Thanks, got a link to upstream report? unfortunately no link, the test suite asks for sending email to yaz-help@indexdata, but got a reply a while ago: ... > and it fails also on ARM, so likely it's related to the char type > being unsigned by default on these 3 arches. A test build with > -fsigned-char made the error in test_embed_record to disappear. Thanks. That makes perfectly sense. We'll fix it. / Adam
Created attachment 741672 [details] fix from upstream
yaz-4.2.56-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/yaz-4.2.56-2.fc19
Package yaz-4.2.56-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing yaz-4.2.56-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7108/yaz-4.2.56-2.fc19 then log in and leave karma (feedback).
yaz-4.2.56-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.