On Fri, Jul 09, 1999, Lenny Foner wrote:
> autoconf work I've got, SSLeay compiled effortlessly under HPUX 9 and
> 10, Solaris, NetBSD, Linux (4.2 and 5.1), Irix (32 and 64 bit), Alphas
> (64 bit, or course) and probably some other OS's I'm forgetting---all
> simply by typing ./configure and then make.
With OpenSSL, you type ./config and then make. :)
Most of the actual problems we have been having are caused by compiler
bugs in the Sun, IRIX and HPUX compilers. I don't think autoconf would
really have helped there. Correct me if I'm wrong, though.
> autoconf work in the Windows port? I'd hope not; I'd imagine instead
> that something like CygWin would make this Just Work, but I've never
> ever tried to build anything there.
Sure, with CygWin, Unix script stuff Just Works, but having to install
that is much more of a nuisance than just Perl (which I understand
nowadays comes with the OS anyway).
> Note in particular this line:
> checking which DES optimizations to use... -DDES_RISC2 -DDES_PTR
Nice, but in some cases it is better to actually know what you are doing
than just pick some flags and try if it appears to work.
Your autoconf log doesn't show signs of the more interesting parts of the
OpenSSL config process such as testing for the CPU version of x86 machines
or creating the assembler files.
There is a long list of checks. What would have happened if for example
"ln -s" had failed or "strings.h" or "unistd.h" had not been
available?
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
