lør, 2003-03-29 kl. 15:42 skrev Philip Hazel:
> > Now an explanation as to why I'm not getting (and never have got)
> > segfaults with two separate versions of Openssl linked in? Or why Exim
> > should be looking for 2 separate versions at compile time?
>
> The various options you supply that end up in the Makefile are what
> controls where Exim looks - and also there are whatever defaults are set
> up on your system. An analysis of the output of the "make" command is
> how one could tell what the build actually used. The -I items on compile
> commands show where it looks for include files, and the -L items on link
> commands show where it looks for libraries to link with. But as I said,
> there are also the inbuilt defaults to consider.
In Local/Makefile I have the ssl libs as:
SUPPORT_TLS=yes
TLS_LIBS=-L/usr/local/ssl/lib -lssl -lcrypto
That's supposed to be Openssl 0.9.7a, libssl.so.0.9.7. However,
libssl.so.0.9.6 is there too. I /could/ rip it out, but I'm a coward.
libcrypto of both is also there.
Why is Exim linking in both at once (ldd shows it is)? Other services
and utilities, such as Openldap 2.1.16, aren't; they choose the
highest/newest version. Is Exim finding things in 0.9.6 it can't find in
0.9.7a?
If Openldap, for example, or GQ (an LDAP client for Gnome), link to
different library versions at once, they croak and segfault - this is an
FAQ thing, by now.
Sorry, I should go through the Exim code/headers, but I'm not C coder
nor analyst.
Best,
Tony
--
Tony Earnshaw
e-post: tonni@???
www: http://www.billy.demon.nl
