> Perhaps the problem is SERF-1 instead of SERF-2 (which is not detected but config.log looks for it)? no idea. I am not sure what you mean with SERF-2. serf-1.3.8 is the current release, 1.3.9 and 1.4.0 are being worked on.