Re: an experiment using mbed TLS

Nick wrote:
> A bit premature here.  I quickly ran ./configure before work and
> configure worked OK.  But tonight, run make, my linker bombed out with:
> 
> /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld:
> cannot find
> -libmbedtls /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld:
> cannot find
> -libmbedx509 /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld:
> cannot find -libmbedcrypto
> 
> Strange, as ldconfig -v reveals:
> 
> /usr/local/lib:
> 	libmbedcrypto.so.0 -> libmbedcrypto.so.2.3.0
> 	libmbedtls.so.10 -> libmbedtls.so.2.3.0
> 	libmbedx509.so.0 -> libmbedx509.so.2.3.0
> 
> Anyway, an hour of investing, it turns out the linker flags are
> incorrect - changing in configure fixed it up:
> 
>   if test "x$ssl_ok" = "xyes"; then
>     LIBSSL_LIBS="-libmbedtls -libmbedx509 -libmbedcrypto"
> 
> Should be -lmbedtls, -lmbedx509 and -lmbedcrypto
> 
> All really does build fine now :)
> 
> mbedtls seems to work well - seems a tad quicker too.

I don't know where you got the
"-libmbedtls -libmbedx509 -libmbedcrypto" from.
Mine has "-lmbedtls -lmbedx509 -lmbedcrypto",
and it says "-lmbedtls -lmbedx509 -lmbedcrypto when
I double-check on hg.dillo.org.