crypto/opensslconf.h.in by Ulf). I don't see any need for it, so I've
folded the whole mumbo-jumbo to #undef BF_PTR:-)
If BF_PTR should normally not be defined, we can simply remove it
from opensslconf.h and the Configure script. Is that what you mean?
(As long as it is in opensslconf.h.in,
crypto/opensslconf.h.in by Ulf). I don't see any need for it, so I've
folded the whole mumbo-jumbo to #undef BF_PTR:-)
If BF_PTR should normally not be defined, we can simply remove it
from opensslconf.h and the Configure script. Is that what you mean?
NO! That's defintely *NOT* what I
On the other hand! Does the library actually *compile* under
MS-DOS/WIN16? Does *anybody* actually use it?
I think Steve still builds Win16 versions.
No I don't. Win16 is too painful but when dropping support was mentioned
a while ago someone mentioned various applications that used
At 17:45 20.04.99 +0200, you wrote:
I myself would vote for the first alternative unless someone can either:
- confirm that *(unligned long *)((unsigned char *)p+i~7) generates the
unwanted unaligned load instruction on Alpha;
- confirm that the library compiles and works under MS-DOS and
#if !defined(BF_PTR) !defined(BF_PTR2)
#define BF_PTR
#endif
i.e. the comment is effectively *disregarded*, isn't it?
This is autogenerated in Configure.
Oops! I suppose I owe an apology for my comment following the quoted
string then. I apologize and I'm sorry!
BUT! Even after
Bottom line. "#define BF_LONG unsigned int" still makes perfect sense on
all (well, at least on mentioned:-) platforms.
Your patch is in the CVS. Please review the current CVS version or
snapshot.
On the other hand! Does the library actually *compile* under
MS-DOS/WIN16? Does *anybody*
Ulf Möller wrote:
Bottom line. "#define BF_LONG unsigned int" still makes perfect sense on
all (well, at least on mentioned:-) platforms.
Your patch is in the CVS. Please review the current CVS version or
snapshot.
On the other hand! Does the library actually *compile* under
Hello again!
I wrote:
#elif defined(BF_PTR)
/* This is normally very good */
#define BF_ENC(LL,R,S,P) \
LL^=P; \
LL^= (((*(BF_LONG *)((unsigned char *)(S[ 0])+((RBF_0)BF_M))+ \
*(BF_LONG *)((unsigned char *)(S[256])+((RBF_1)BF_M)))^ \
On Tue, Apr 20, 1999 at 06:14:36PM +0100, Dr Stephen Henson wrote:
proposal to include the .err files instead of copying them in.
Personally I'm against this. It'll just be extra baggage to install (and
get working cross platform) and extra dependencies with IMHO minimal
benefits.
Hoewever
Hi! Following is far from what I'd consider as a good programming
practice... First a trivial table everybody would recognize:
Intel,SPARCv8,MIPS 32 Alpha,SPARCv9,MIPS 64
sizeof(int) 4 4
sizeof(long)4 8
10 matches
Mail list logo
