Hi, The newly uploaded (to experimental) version 1.8.0 uses an internal crypto engine instead of libgcrypt. It reads from /dev/urandom instead of using libgcrypt. I believe libgcrypt initialize its RNG pool from /dev/random. Thus, I would expect that this problem goes away with 1.8.0 assuming your build hosts has a working /dev/urandom.
/Simon -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
