Comment #6 on issue 74 by dsallings: configure script incorrectly
identifies sparc v9 as little endian, selecting incorrect hash function.
http://code.google.com/p/memcached/issues/detail?id=74
Great. There is an issue with configure caching, so it's possible that
running
configure twice
Comment #5 on issue 74 by robert.coles: configure script incorrectly
identifies sparc v9 as little endian, selecting incorrect hash function.
http://code.google.com/p/memcached/issues/detail?id=74
I've been trying to recreate the issue.. and no joy.. it was a colleague
who did the initial
Updates:
Status: Fixed
Comment #4 on issue 74 by dsallings: configure script incorrectly
identifies sparc v9 as little endian, selecting incorrect hash function.
http://code.google.com/p/memcached/issues/detail?id=74
I was not able to build an automated test that fails this (without
Comment #3 on issue 74 by mjhostetter: configure script incorrectly
identifies sparc v9 as little endian, selecting incorrect hash function.
http://code.google.com/p/memcached/issues/detail?id=74
FWIW I previously sent a patch against 1.4.0 to fix incorrect reuse of the
ac_cv_c_endian variab
Comment #2 on issue 74 by trond.norbye: configure script incorrectly
identifies sparc v9 as little endian, selecting incorrect hash function.
http://code.google.com/p/memcached/issues/detail?id=74
FYI, I tried this on a T5240 running Solaris 10 with gcc 4.4.0 and Sun
Studio 12 without any
Updates:
Status: Started
Comment #1 on issue 74 by dsallings: configure script incorrectly
identifies sparc v9 as little endian, selecting incorrect hash function.
http://code.google.com/p/memcached/issues/detail?id=74
I've written a test for this bug against 1.4.0+ and I'm not findi
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 74 by robert.coles: configure script incorrectly identifies sparc
v9 as little endian, selecting incorrect hash function.
http://code.google.com/p/memcached/issues/detail?id=74
What steps will reproduce the problem?
1. com