Problems with auto::crypto have not reoccurred on Darwin. They have
occurred on Cygwin, but that's better handled in a different ticket. So
I'm resolving this one.
Andy Dougherty wrote:
On Sat, 15 Mar 2008, James Keenan via RT wrote:
On Sat Mar 15 10:50:04 2008, doughera wrote:
Ah, I think this one is easy: If I recall correctly, the SHA256_CTX
stuff was added in openssl version 0.9.8; I'll bet your system has
0.9.7.
Yes.
OpenSSL> version
OpenSSL 0.
On Sat Mar 15 16:51:14 2008, doughera wrote:
>
> Why wait for someone else? This trivial patch (untested, but it
> really
> should be this easy) ought to implement (1). This way you can proceed
> without waiting for any broader discussion.
>
Thanks, Andy. Applied in r26405. With it, I get th
On Sat, 15 Mar 2008, James Keenan via RT wrote:
> On Sat Mar 15 10:50:04 2008, doughera wrote:
>
> > Ah, I think this one is easy: If I recall correctly, the SHA256_CTX
> > stuff was added in openssl version 0.9.8; I'll bet your system has
> > 0.9.7.
> >
>
> Yes.
>
> OpenSSL> version
> OpenSS
On Sat Mar 15 10:50:04 2008, doughera wrote:
> Ah, I think this one is easy: If I recall correctly, the SHA256_CTX
> stuff was added in openssl version 0.9.8; I'll bet your system has
> 0.9.7.
>
Yes.
OpenSSL> version
OpenSSL 0.9.7l 28 Sep 2006
> Two reasonable fixes:
>
> 1. (Easy) Change
On Sat, 15 Mar 2008, James Keenan wrote:
> config/auto/crypto.pm was committed to trunk on March 14 by fperrad.
[ lots of irrelevant successful items trimmed ]
> /usr/bin/gcc-3.3 -c -o sha256.o [lots of flags] sha256.c
> ./sha256.pmc: In function `Parrot_SHA256_clone':
> ./sha256.pmc:77: error:
