Re: #include foo.h or #include openssl/foo.h?

1999-04-24 Thread Ulf Möller
special case. It'll have to be pretty severe to justify breaking the entire existing code base. How about keeping symlinks in place for a transition period? Then old applications can be built unmodified, but if a name conflict occurs the user can simply rm -f include/*.h After some time

Re: Issue with building OpenSSL-0.9.1c under Solaris2.6

1999-04-24 Thread Bodo Moeller
Ian Pollard [EMAIL PROTECTED]: Description: Cannot build OpenSSL-0.9.1c under Solaris 2.6 with Sun C compiler OpenSSL-0.9.1c You should use 0.9.2b (with the no-asm option) or even better 0.9.3, which unfortunately isn't finished yet though. Or get the current snapshot. "bn_mul.c", line