On Mon, Jun 29, 2015 at 12:57:27PM -0700, Seth wrote:
> On Mon, 29 Jun 2015 12:55:21 -0700, Gilles Chehade <[email protected]> wrote:
> >what is is that you experience in this setup ?
> >it builds but fails at startup ?
>
> It build and runs fine, however the binaries is not linked to the latest
> libssl in /usr/local/lib. Only the libcrypto lib is correctly linked.
>
I was kinda puzzled then miod@ clarified for me, /usr/lib has priority
over /usr/local/lib, if a lib is available in both the one in /usr/lib
is the one used.
Small snippet from cc(1):
The directories searched include several standard system
directories *plus* any that you specify with -L.
It is an environment/host issue, I do not know if it can be fixed with
a build option at this point, it needs investigating, I honestly don't
have a clue if it can be worked-around.
I suggest you ask on [email protected] for suggestions on how to do it,
if it has worked in the past then the ld.so people may have changed it
because our Makefile certainly has not changed.
In the meantime, you can work around at runtime using LD_LIBRARY_PATH:
$ ldd smtpd/smtpd|grep -E "lib(ssl|crypto)"
00001d2e3b43c000 00001d2e3b89b000 rlib 0 1 0
/usr/lib/libssl.so.32.0
00001d2e52d38000 00001d2e53308000 rlib 0 2 0
/usr/lib/libcrypto.so.33.0
$ LD_LIBRARY_PATH=/usr/local/lib ldd smtpd/smtpd|grep -E "lib(ssl|crypto)"
0000141edd36f000 0000141edd7ce000 rlib 0 1 0
/usr/local/lib/libssl.so.32.0
0000141fb51a0000 0000141fb5770000 rlib 0 2 0
/usr/local/lib/libcrypto.so.33.0
$
--
Gilles Chehade
https://www.poolp.org @poolpOrg
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
