Tabor,
You made me look at this one more time and I found the problem:
Somewhere I read that I can have both the following in my makefile:
TLS_LIBS = -L/usr/local/ssl/lib -lssl -lcrypto
TLS_LIBS = -R/usr/local/ssl/lib -lssl -lcrypto
So I did that.
When I recompiled exim with "TLS_LIBS = -L/usr/local/ssl/lib -lssl -lcrypto"
only, the resulting binary didn't give me any trouble.
I'll monitor things over the next week. Thanks to all who have helped me
out. The exim-users group has been very responsive.
Regards,
Gary Ferrer.
----- Original Message -----
From: "Tabor J. Wells" <twells@???>
To: "Gary Ferrer" <gary@???>
Cc: "Exim Users" <exim-users@???>
Sent: November 12, 2001 2:36 PM
Subject: Re: [Exim] LD/Exim errors
> On Mon, Nov 12, 2001 at 12:18:37PM -0800,
> Gary Ferrer <gary@???> is thought to have said:
>
> > I can start exim no problem. However, if I reboot the server, I get
> > the
> > same error as above when exim starts up. I started looking at the
> > problem
> > but still haven't solved it. For exim to have compiled with ssl, my
> > makefile would have had the location of the libraries, so why doen't
> > it know
> > where they are?
>
> Because root's environment at startup time has a limited LD_LIBRARY_PATH
> set. It hasn't sourced your .profile (or whatever you used to define those
> variables). The following works for me on Solaris (in my Local/Makefile):
>
> #TLS/SSL encryption support
> SUPPORT_TLS = yes
> TLS_LIBS = -L/usr/local/ssl/lib -lssl -lcrypto
> TLS_INCLUDE = -I/usr/local/ssl/include
>
> Tabor
>
> --
> --------------------------------------------------------------------
> Tabor J. Wells twells@???
> Fsck It! Just another victim of the ambient morality
>
