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 this and not #include <crypt.h> ?
Things compile fine without <crypt.h> being included, in the case of
OpenSSL support being needed. As the problem appears to be in
already-released versions of OpenSSL, wouldn't the best approach be to
notify the OpenSSL guys (they're decent people, and CC'ing this now to
their developer list) and also work around the problem ourselves?
Regards and best wishes,
+ Justin Clift
Peter Eisentraut wrote:
> Justin Clift writes:
> > When --with-openssl=<the path to my openssl dir> 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.
In response to
pgsql-bugs by date
|Next:||From: pgsql-bugs||Date: 2001-03-25 14:05:59|
|Subject: --enable-perl doesn't like Solaris|
|Previous:||From: Justin Clift||Date: 2001-03-25 13:03:45|
|Subject: Re: Various bugs with PG7.1 8th March snapshot on Solaris 8 INTEL|