> --- crypto/perlasm/x86_64-xlate.pl~     2010-10-10 22:14:17.000000000 +0100
> +++ crypto/perlasm/x86_64-xlate.pl      2011-01-18 16:49:06.000000000 +0000
> @@ -66,7 +66,7 @@
>    my ($outdev,$outino,@junk)=stat($output);
>
>      open STDOUT,">$output" || die "can't open $output: $!"
> -     if ($stddev!=$outdev || $stdino!=$outino);
> +     if (!defined($outdev) || $stddev!=$outdev || $stdino!=$outino);
>  }
>
>  my $gas=1;     $gas=0 if ($output =~ /\.asm$/);

This patch works. Andy Piper's patch in RT#2440 also works.

> --- crypto/sha/Makefile~        2008-11-12 08:19:03.000000000 +0000
> +++ crypto/sha/Makefile 2011-01-18 17:06:15.000000000 +0000
> @@ -61,8 +61,8 @@
>
>  # Solaris make has to be explicitly told
>  sha1-x86_64.s:       asm/sha1-x86_64.pl;     $(PERL) asm/sha1-x86_64.pl 
> $(PERLASM_SCHEME) > $@
> -sha256-x86_64.s:asm/sha512-x86_64.pl;        $(PERL) asm/sha512-x86_64.pl 
> $(PERLASM_SCHEME) $@
> -sha512-x86_64.s:asm/sha512-x86_64.pl;        $(PERL) asm/sha512-x86_64.pl 
> $(PERLASM_SCHEME) $@
> +sha256-x86_64.s:asm/sha512-x86_64.pl;        $(PERL) asm/sha512-x86_64.pl 
> $(PERLASM_SCHEME) > $@
> +sha512-x86_64.s:asm/sha512-x86_64.pl;        $(PERL) asm/sha512-x86_64.pl 
> $(PERLASM_SCHEME) > $@
>  sha1-sparcv9.s:      asm/sha1-sparcv9.pl;    $(PERL) asm/sha1-sparcv9.pl $@ 
> $(CFLAGS)
>  sha256-sparcv9.s:asm/sha512-sparcv9.pl;      $(PERL) asm/sha512-sparcv9.pl 
> $@ $(CFLAGS)
>  sha512-sparcv9.s:asm/sha512-sparcv9.pl;      $(PERL) asm/sha512-sparcv9.pl 
> $@ $(CFLAGS)

This does not and I am not sure why.

Tony.
-- 
f.anthony.n.finch  <[email protected]>  http://dotat.at/
HUMBER THAMES DOVER WIGHT PORTLAND: NORTH BACKING WEST OR NORTHWEST, 5 TO 7,
DECREASING 4 OR 5, OCCASIONALLY 6 LATER IN HUMBER AND THAMES. MODERATE OR
ROUGH. RAIN THEN FAIR. GOOD.


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to