I just compiled the 9.9-dev version from the 12022007 tarball under
DJGPP. There were only 2 changes needed, one for b_sock.c, since DJGPP
with WATT32 doesn't define socklen_t and one for testtsa to handle DOS
style path separators. I also noted what seems to be a typographical
error in ts.pod.
In message [EMAIL PROTECTED] on Sun, 2 Dec 2007 23:47:05 -0800 (PST), Doug
Kaufman [EMAIL PROTECTED] said:
dkaufman I just compiled the 9.9-dev version from the 12022007 tarball under
dkaufman DJGPP. There were only 2 changes needed, one for b_sock.c, since DJGPP
dkaufman with WATT32 doesn't
I know this must have been answered elsewhere, but I have not found it:
How does one build and use gmp on powerpcc64 on debian?
I have done:
543 ./Configure --prefix=~gries/usr/local/ssl
--openssldir=~gries/usr/local/ssl gcc -DUSE_TOD threads shared enable-idea
enable-rc5 enable-mdc2
Output seems to be 16-bit .. Please
regenerate disassembler listings.
done; and I believe the issue shows already up in the first lines at 0014:
Metrowerks:
http://www.gknw.net/test/openssl/0.9.8-stable/mwasm/rm-nw.dis
NASM:
http://www.gknw.net/test/openssl/0.9.8-stable/nasm/rm-nw.dis
the
This bug report is related to a problem that has been solved already for Linux
systems in patch 0.9.8c. It has also been pointed out in open Ticket #1298. (Is
it possible that this ticket was the root of the Linux fix? If so maybe status
should be changed in the Ticket.)
Patch:
$ cvs -d/Users/kylehamilton/workspace/openssl-repo co openssl
$ cd openssl
$ cvs update -t FIPS_098_TEST_8
I'm going to assume that I need to follow the CONFIG.FIPS file, and use:
$ ./config fipscanisterbuild
'make' completes (Mac OS X 10.4.11 Intel).
'make test' completes. It
On related note question is what prevents you from always using nasm? Or
rather do we actually need to support for metrowerks assembler?
Basically if there is one working configuration for netware, what do we
need second one for?
well, that wasnt my idea, but it was 'historically'. I guess The
It's not about amount, but rather about not willing to support something
that is commonly tested.
I naturally meant not willing to support something that is *not*
commonly tested. A.
__
OpenSSL Project
I just opened the README.FIPS myself, and was looking at the Windows
build process and came across this:
With this version the use of MinGW is unnecessary and the normal VC++
build procedure can be followed *except* the GNU linker ld.exe
(for example from MinGW) must be accessible somewhere on
Well even though I get the error about the shared libraries, it did work with
is Configure:
./Configure --prefix=~gries/usr/local/ssl --openssldir=~gries/usr/local/ssl
threads linux-ppc64 -m64 -L/usr/local/lib -DOPENSSL_USE_GMP -lgmp -static
[EMAIL PROTECTED]:~/openssl-0.9.8g$
Hi Andy,
Is it possible to link object modules compiled with nasm with object
modules compiled with codewarrior? It might appear as silly question,
but I know nothing about netware, while it sounds like some of netware
development environments are cross-compile...
yes. There are a couple of
Well it did not use gmp. It ran faster but from oprofile it ran bn. I would
have thought that it should run faster with gmp from gmpbenchmark:
* GMPbench version 0.1 *
Using default CFLAGS = -O5 -m64 -I/proj/ext3/users/gries/math/gmp-4.2.1
Using default CC = gcc
Using default LIBS =
On Mon, Dec 03, 2007, Andy Polyakov wrote:
I just opened the README.FIPS myself, and was looking at the Windows
build process and came across this:
With this version the use of MinGW is unnecessary and the normal VC++
build procedure can be followed *except* the GNU linker ld.exe
(for
Is it possible to link object modules compiled with nasm with object
modules compiled with codewarrior? It might appear as silly question,
but I know nothing about netware, while it sounds like some of netware
development environments are cross-compile...
yes. There are a couple of different
vanilla COFF and latest nasm versions; check self:
D:\openssl-SNAP-20071203\crypto\aes\asmaes-586.pl nw-nasm a-nw.asm
D:\openssl-SNAP-20071203\crypto\aes\asmnasmw -v
NASM version 0.99.06 compiled on Nov 1 2007
D:\openssl-SNAP-20071203\crypto\aes\asmnasmw -s -f coff a-nw.asm -o a-nw.o
a-nw.asm:4
Hi,
while trying to add the AES asm support I found that currently in HEAD the
AES asm part is missing in mk1mf.pl - my patch does also add this part
which I copied over from 0.9.8-stable where its included;
however it seems that I'm missing something since it doesnt work:
while I get the asm
16 matches
Mail list logo
