On Fri, 20 May 2005, Andy Polyakov wrote:
make[1]: Entering directory `/usr/local/src/libs/openssl-0.9.8/crypto'
gcc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -mcpu=pentium -DL_ENDIAN -DTERMIO
-O3 -fomit-frame-pointer -Wall -DOPENSSL_BN
Hi,
now that I had first contact with engines, I thought it might be
better to give them some testing.
It turns out that loading the engines works fine, but there are three
engines which don't work, and it seems to me that this isn't a Cygwin
specific problem.
These three engines don't load:
Hi Andy,
On May 21 22:36, Andy Polyakov wrote:
> Speaking of documentation:-) Is cygwin memory layout documented
> somewhere? What I'm trying to ask is if you can provide a pointer. If
> it's documented in commentary section in source code, then could you be
> so kind to give some approximate d
tim> > Hmm... I personally do not support SCO products for political
tim> > reasons, so I'm not going to offer much about them. However,
tim> > it looks like the CC and CFLAGS variables do not follow along
tim> > in the build for some of your platforms, and that has me a bit
tim> > worried. I'l
In message <[EMAIL PROTECTED]> on Sat, 21 May 2005 19:21:20 -0700 (PDT), Tim
Rice <[EMAIL PROTECTED]> said:
tim> On Fri, 20 May 2005, Richard Levitte - VMS Whacker wrote:
tim>
tim> > In message <[EMAIL PROTECTED]> on Thu, 19 May 2005 22:14:20 -0700 (PDT),
Tim Rice <[EMAIL PROTECTED]> said:
tim>
