That sounds like The Right Way of doing it; most responsible,
technically sound, etc.
Regards and best wishes,
Justin Clift
Larry Rosenman wrote:
> I suspect renaming it would be the best way, since we have 2 major
> (SUN, SCO) vendors claiming a des_encrypt() function in their libcrypt
> and
* Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> [010325 14:41]:
> From: Larry Rosenman <[EMAIL PROTECTED]>
>
> ler> * Justin Clift <[EMAIL PROTECTED]> [010325 07:34]:
> ler> > Hi Peter,
> ler> >
> ler> > Can't this be at least worked around by ./configure detecting there will
> ler> > be a c
* Justin Clift <[EMAIL PROTECTED]> [010325 07:34]:
> Hi Peter,
>
> Can't this be at least worked around by ./configure detecting there will
> be a conflict (i.e. being compiled with OpenSSL support on Solaris or
> Unixware) then creating something like #define
> OPENSSL_DES_ENCRYPT_NAMESPACE_CONF
Justin Clift writes:
> Has anything else regarding general broken int8 tests been found out,
> with regards to it being caused by OpenSSL. If that's the case
> shouldn't we ask the OpenSSL guys about known issues, or at least let
> them know that something may be wrong?
This has been fixed. It
Hi Peter,
Can't this be at least worked around by ./configure detecting there will
be a conflict (i.e. being compiled with OpenSSL support on Solaris or
Unixware) then creating something like #define
OPENSSL_DES_ENCRYPT_NAMESPACE_CONFLICT in the Makefile, and then having
crypt.c (etc) check for t
Tom Lane writes:
> Maybe the AC_TRY_RUN tests could be moved up to before we start probing
> for libraries?
The overall order of the tests should stay this way, I think. Some
library could actually alter the result of a run test. (Think about some
-lcompat or -lbsd getting in the way, not unli
Tom Lane writes:
> >> Er ... what? Why would the test program be trying to use that shlib?
>
> > Because -lssl is added to LIBS, the test program is linked against LIBS,
> > and when the program starts it tries to locate all the dependent libraries
> > (not matter if it doesn't actually have to
Tom Lane writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> >> IIRC, someone else reported a few days ago that the int8 tests failed on
> >> their platform if and only if openssl was linked in. Not sure what
> >> openssl could be doing to screw up long long int arithmetic, but that
> >> wa
Tom Lane writes:
> IIRC, someone else reported a few days ago that the int8 tests failed on
> their platform if and only if openssl was linked in. Not sure what
> openssl could be doing to screw up long long int arithmetic, but that
> was the report.
Of course! The test program aborts because
Justin Clift writes:
> When --with-openssl= is given to configure
> on Solaris 8 INTEL, the compilation errors in :
This is an OpenSSL namespace problem on some platforms (Solaris, Unixware
so far). Nothing we can really do about it.
> Next problem is that running 'gmake check' expects to find
10 matches
Mail list logo
