You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. build memcached with Sun Fire T2000 under Debian
What is the expected output? What do you see instead?
The build fail with:
[...]
ok 25 - binary_replace
testapp: testapp.c:725: safe_recv: Assertion `nr != 0' failed.
make[1]: *** [test] Aborted
Makefile:1482: recipe for target 'test' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test: make -j30 test returned exit code 2
make: *** [build-arch] Error 2
debian/rules:45: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
What version of the product are you using? On what operating system?
1.4.24 on Debian sparc unstable
Please provide any additional information below.
This bug seems quite similar to
https://code.google.com/p/memcached/issues/detail?id=404 which is about 1.4.23.
Informations on Debian sparc: https://www.debian.org/ports/sparc/
Spac build machine (for model/config):
https://db.debian.org/machines.cgi?host=stadler
Original issue reported on code.google.com by [email protected] on 29 Jun 2015 at 8:56
The text was updated successfully, but these errors were encountered:
I need more information. can you get a backtrace? do the perl tests pass?
prove -v t/binary.t might be helpful. that looks like it failed on the
binary_replaceq, but I don't have any clues as to why that'd happen.
Complete build log can be found here:
https://buildd.debian.org/status/fetch.php?pkg=memcached&arch=sparc&ver=1.4.24-1
&stamp=1432598378.
I don't have any setup to reproduce it and it seems to be difficult to found
installation media for Debian unstable (the arch need porter manpower) and not
sure that qemu emulation could help to reproduce.
I'll try a bit to work on that.
Well, i think we can leave this bug opened for the record, but i don't
investigate more on this because Debian Sparc is "dead":
https://lists.debian.org/debian-sparc/2015/07/msg00012.html
Original issue reported on code.google.com by
[email protected]
on 29 Jun 2015 at 8:56The text was updated successfully, but these errors were encountered: