-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 0.9.7i released
===
OpenSSL - The Open Source toolkit for SSL/TLS
http://www.openssl.org/
OpenSSL 0.9.7h caused crashes when the shared libcrypto was
upgraded. This release fixes that pr
[guest - Fri Oct 14 20:59:40 2005]:
Its a compiler issue i got it resolved thnx.
> Hi,
>
> I am trying install openssl-0.9.7b on solaris box.
>
> I ran ./config first, it went fine with out any errors
>
> when I ran make I got compilation error with cc not recognizing certain
> options
>
> F
Hi,
I am trying install openssl-0.9.7b on solaris box.
I ran ./config first, it went fine with out any errors
when I ran make I got compilation error with cc not recognizing certain
options
First I ran
command: ./config
this command went fine
command:./config -t
output:
MIKE DEBUG GCCVER i
Hi,
I am trying install openssl-0.9.7b on solaris box.
I ran ./config first, it went fine with out any errors
when I ran make I got compilation error with cc not recognizing certain
options
First I ran
command: ./config
this command went fine
command:./config -t
output:
MIKE DEBUG GCCVER i
Hello,
I'm using an Solaris 10 on AMD Opteron, and I'm trying to compile in
32bit mode (solaris-x86-gcc), but I've a Segmentation Fault.
Here's testlog file as attachment.
To help, the same compilation in 64bit mode (solaris64-x86_64-gcc) works
fine but I can't compile Apache with it.
And with
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi all,
i'd reported both of these when 0.9.8 first came out.
as of the 098a release, they're still, apparently, unresolved.
(1)
building 0.9.8a on OSX 10.4.2,
'make install' fails @
...
making install in engines...
i
Using openssl-0.9.8a or openssl-0.9.8-stable-SNAP-20051013, and the
configuration "./Configure BSD-x86-elf 386 no-shared no-ssl2" on
FreeBSD 5.3 or a similar command line on Solaris 8, the make fails:
( :;LIBDEPS="${LIBDEPS:--L.. -lssl -L.. -lcrypto }";
LDCMD="${LDCMD:-gcc}"; LDFLAGS="${LD
On 2005.10.13 at 13:27:47 -0700, Howard Chu wrote:
> Disregard that comment, I was lost. I don't interchange MSVC / gcc dll's
> on the fly. I was just thinking about the import libraries; a
> gcc-compiled DLL will work with an MSVC app if it's linked with the
> gcc-specific import library, and
On 2005.10.13 at 12:42:34 -0700, Howard Chu wrote:
>
> We already build using the mingw32 compiler under msys. I've been a bit
> lax about sending back patches lately, but as I recall there were only a
> few small tweaks to Configure needed. IMO the Cygwin environment is
> worthless; it is sev