* Justin Clift <jclift@iprimus.com.au> [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_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?
I've been in contact with an OpenSSL guy, and given him a shell
account here. He's looking into it.
LER
>
> 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.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
