- Dec 20, 2001
-
-
Richard Levitte authored
-
Richard Levitte authored
-
Richard Levitte authored
-
Richard Levitte authored
-
Richard Levitte authored
-
Richard Levitte authored
-
- Dec 11, 2001
-
-
Richard Levitte authored
-
Richard Levitte authored
1. some platforms do not have inttypes.h, and chasing them down becomes ridiculous. Therefore, uint64_t can't be used for 64-bit values. 2. some (other) platforms do not support "long long". Solution: make AEP_U64 a struct with two longs unless long already is 64 bit long. Also, restore all other types back to use unsigned char, unsigned int and unsigned long. Make sure that AEP_U32 actually becomes 32 bits, even on platforms where long is 64 bits (actually, we're just guessing that int will stay at 32 bits on those...).
-
- Nov 28, 2001
-
-
Richard Levitte authored
-
- Nov 24, 2001
-
-
Geoff Thorpe authored
-
- Nov 23, 2001
-
-
Bodo Möller authored
-
Bodo Möller authored
-
- Nov 21, 2001
-
-
Richard Levitte authored
branches.
-
Richard Levitte authored
-
Richard Levitte authored
built-in types __int8, __int16 and so on on that platform.
-
Geoff Thorpe authored
-
- Nov 20, 2001
-
-
Geoff Thorpe authored
-
- Nov 19, 2001
-
-
Richard Levitte authored
Extentions of the explanations to the linking problem on Win32. Provided by Andrew Gray <agray@iconsinc.com>
-
- Nov 17, 2001
-
-
Richard Levitte authored
32-bit platforms. Instead, make use of inttypes.h and use the types defined there to get 8-, 16-, 32- an 64-bit values. There might be some operating systems where one should use int_types.h instead of inttypes.h. Unfortunately, I don't recall which one(s).
-
Geoff Thorpe authored
-
Geoff Thorpe authored
be included for 0.9.6c-engine.
-
- Nov 16, 2001
-
-
Richard Levitte authored
-
Richard Levitte authored
-
Richard Levitte authored
compile properly).
-
- Nov 15, 2001
-
-
Richard Levitte authored
make update perl util/mkerr.pl -recurse -write -rebuild (now, just look at the effect that last thing had on the ENGINE error strings! How did that unbalance between macros and strings happen?)
-
Richard Levitte authored
-
Geoff Thorpe authored
Also, the "to" variable used in cleanup is never non-NULL and is entirely unused. As such, the cleanup might have been missed under genuine error conditions and caused leaks and/or returned invalid pointers.
-
Geoff Thorpe authored
to be pointless.
-
- Nov 13, 2001
-
-
Bodo Möller authored
-
Bodo Möller authored
-
- Nov 12, 2001
-
-
Bodo Möller authored
-
Mark J. Cox authored
patches taken from Red Hat Linux 7.2. Original code from Broadcom with patches and backport by Nalin, more backport to fix warnings and const changes by Mark Submitted by: Mark Cox Reviewed by: PR:
-
Mark J. Cox authored
for acceleration only at the moment, but full key management is being worked on for the future. This code has been compiled cross-platform but not extensively tested Submitted by: Mark Cox, Baltimore Technologies Reviewed by: Mark Cox PR:
-
Mark J. Cox authored
Submitted by: Reviewed by: PR:
-
Mark J. Cox authored
7.2 and been given extensive testing; it also compiles okay on our selection of random machines (including 64-bit) Submitted by: AEP, Mark Cox Reviewed by: Mark Cox PR:
-
- Nov 10, 2001
-
-
cvs2svn authored
0_9_6-stable'.
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
Important SSL 2.0 bugfixes (bugs found while implementing msg_callback).
-