Applied. Thanks.
[EMAIL PROTECTED] - Sun Jun 19 13:16:19 2005]:
> I tried compiling with DJGPP using your patch applied to beta5. It
> compiles OK, but there are a lot of warnings, since there is a default
> definition of DEVRANDOM earlier in the e_os.h file. I applied this
> patch.
>
> --- e_
On Sat, 18 Jun 2005, Richard Levitte via RT wrote:
> The real issue was the backslahes in the configuration definition for
> DJGPP and how those interacted with the handling of a build environment
> in the Makefiles.
>
> I resolved the issue by moving the definition of DEVRANDOM for DJGPP
> f
On Sat, 18 Jun 2005, Richard Levitte via RT wrote:
> The real issue was the backslahes in the configuration definition for
> DJGPP and how those interacted with the handling of a build environment
> in the Makefiles.
>
> I resolved the issue by moving the definition of DEVRANDOM for DJGPP
> fr
The real issue was the backslahes in the configuration definition for
DJGPP and how those interacted with the handling of a build environment
in the Makefiles.
I resolved the issue by moving the definition of DEVRANDOM for DJGPP
from Configure to e_os.h.
[guest - Mon Jun 13 11:45:04 2005]:
>
Since 0.9.8beta3 method RAND_pool, when DEVRANDOM is defined, don't read
data from specified devices.
before:
$ strace -f openssl genrsa 2>&1 | grep -i random
open("/dev/urandom", ...) = 3
after:
$ strace -f openssl genrsa 2>&1 | grep -i random
open("DEVRANDOM", ...) = -1 ENOENT ...
solution -
