> This was already requested in #2049
> /Ann.
> ***
> issue:
> X509 certificate serial numbers are displayed as negative,
> e.g. in
> -BEGIN CERTIFICATE-
> MIIB2zCCAUSgAwIBAgIFAKoSExQwDQYJKoZIhvcNAQEFBQAwNTEzMDEGA1UEAxMq
> TmVnU2VyaWFsIFBLSSBS
> I've noticed a bug regarding white spaces within the directory name of Perl
> binary ($^X) in crypto/x86_64cpuid.pl.
> IIRC this does affect older versions of the 1.0 branch too.
>
> Build fails with the following message:
> set ASM=nasm -f win64 -DNEAR -Ox -g
> perl crypto\x86
>> It must be "perl" thing, rather than "Solaris". This is strange, because
>> I test with rather old perl version, 5.003 and it's not a problem.
>> What's your 'perl -v'? But most interesting question why just
>> aes-sparcv9.pl? Other assembler scripts also have similar expression,
>> without '' a
On 10 January 2012 20:02, Andy Polyakov via RT wrote:
> It must be "perl" thing, rather than "Solaris". This is strange, because
> I test with rather old perl version, 5.003 and it's not a problem.
> What's your 'perl -v'? But most interesting question why just
> aes-sparcv9.pl? Other assembler sc
The workaround for this issue is hat was added for 0.9.8m is only applied in
an #ifdef _MSC_VER codebranch.
This bug is also triggered when building openssl in mingw so it should be
applied for this, too. It might account for reports that users are still
running into this problem with recent ver
Hello,
I've noticed a bug regarding white spaces within the directory name of Perl
binary ($^X) in crypto/x86_64cpuid.pl.
IIRC this does affect older versions of the 1.0 branch too.
Build fails with the following message:
set ASM=nasm -f win64 -DNEAR -Ox -g
perl crypto\x86_64cpu
