Comment 5 for bug 10638

The issue here is that the buildd's (having been started from cron/at), have
RLIMIT_MEMLOCK==0, which causes the test to fail. Building outside of the
buildd (or restarting the buildd from an unlimited shell, etc) corrects the
issue. Spec says that ENOMEM is a valid return, hence the test is broken:
[ENOMEM]
   Locking the pages mapped by the specified range would exceed an
implementation-defined limit on the amount of memory that the process may lock.

Fixed in 1.2.5-3ubuntu3 by #if 0'ing the HAVE_BROKEN_MLOCK variable out of
existance in config.h.in (minimal change)

James - would you take care of forwarding this upstream?