Re: Various bugs with PG7.1 8th March snapshot on Solaris 8INTEL
Justin Clift <jclift@iprimus.com.au>
From: Justin Clift <jclift@iprimus.com.au>
To: Peter Eisentraut <peter_e@gmx.net>, pgsql-bugs@postgresql.org
Cc: openssl-dev@openssl.org
Date: 2001-03-25T13:09:16Z
Lists: pgsql-bugs
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 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.