Thank you for OpenSSL.
I tried to make OpenSSL ver.1.0.0 on MacOSX.
But I failed to 'make test', it said 'Bad cpu type'
Maybe, It is occurred by 'crypto/perlasm/ppc-xlate.pl' .
In 61 lines
$arch = ($flavour=~/64/) ? ppc970-64 : ppc970 if ($arch eq any);
In my environment, $flavour is
I tried to make OpenSSL ver.1.0.0 on MacOSX.
But I failed to 'make test', it said 'Bad cpu type'
Maybe, It is occurred by 'crypto/perlasm/ppc-xlate.pl' .
In 61 lines
$arch = ($flavour=~/64/) ? ppc970-64 : ppc970 if ($arch eq any);
In my environment, $flavour is 'osx32', so $arch
At [http://carnivore.it/2010/03/30/openssl_1.0_benchmark] there is a
comparison chart between 0.9.8g and 1.0.0 where most AES results are
even slower now.
See commentary in crypto/aes/asm/aes-596.pl for explanation. A.
__
--
Without this patch the make will error with Pick one target type
from and a list of assembler types.
mingw32-make: *** [tmp\x86cpuid.asm] Error 1
--
ms\mingw32.bat no-capiengms_make.out 21
cd out
..\ms\test ..\ms_test.out 21
You could use standard build for 1.x+
It's rather should
This version also doesn't compile on both Suse and RedHat on the s390
z-series platform:
gcc -I.. -I../.. -I../../include -DDSO_DLFCN -DHAVE_DLFCN_H -fPIC
-mbackchain -DB_ENDIAN -DTERMIO -O1 -Wall -c -o md4_dgst.o md4_dgst.c
md4_dgst.c: In function 'md4_block_data_order':
md4_dgst.c:115:
We use the following patch on openSUSE to make sure that openssl
uses non-executable stack by marking the assembler code as
not requiring x-stack.
This was discussed earlier. Adding system specifics to code is not
directly desired for obvious reasons. Suggested alternative is configure
with
Hello all,
Check-in [19505] and [19557] cryptlib.c: allow application to override
OPENSSL_isservice adds call for GetProcAddress with argument name of
function that start with underscore.
The function OPENSSL_isservice is specific for windows platforms and on
those platforms in not well
I agree that OPENSSL_isservice() cannot be changed,
??? My suggestion for *you* was to modify it to unconditionally
return 1...
Our application can both run in foreground and in service
context. So
simply changing to return 1 is not possible.
If changing to return 1 is not acceptable, how
What are the impact of replacing ppc970 with ppc7400 ? I've done a build with
this settings and I am wondering whether I should rebuild (using either the
patch or the workaround).
Thanks
__
OpenSSL Project
Roumen Petrov wrote:
Hello all,
Check-in [19505] and [19557] cryptlib.c: allow application to override
OPENSSL_isservice adds call for GetProcAddress with argument name of
function that start with underscore.
The function OPENSSL_isservice is specific for windows platforms and on
those
10 matches
Mail list logo
