ldas-tools @2.4.2 links with libmd5 if libwww port is installed

[ryandesign (Ryan Carsten Schmidt)]

ldas-tools' configure script is engineered to prefer openssl on Linux and to fall back to libmd5 if openssl is not available, but reverses this on other systems to prefer libmd5 and to fall back to openssl if libmd5 is not available.

The libwww port provides libmd5, so if that port is installed when ldas-tools is built, ldas-tools ends up linked with libmd5 and not openssl's libraries. One example:

/opt/local/bin/framecpp_verify:
	/opt/local/lib/libframecpp.6.dylib (compatibility version 7.0.0, current version 7.0.0)
	/opt/local/lib/libframecpp8.4.dylib (compatibility version 5.0.0, current version 5.0.0)
	/opt/local/lib/libframecpp7.2.dylib (compatibility version 3.0.0, current version 3.1.0)
	/opt/local/lib/libframecpp6.5.dylib (compatibility version 6.0.0, current version 6.0.0)
	/opt/local/lib/libframecpp4.5.dylib (compatibility version 6.0.0, current version 6.0.0)
	/opt/local/lib/libframecpp3.3.dylib (compatibility version 5.0.0, current version 5.0.0)
	/opt/local/lib/libframecppcmn.4.dylib (compatibility version 7.0.0, current version 7.0.0)
	/opt/local/lib/libmd5.0.dylib (compatibility version 2.0.0, current version 2.0.0)
	/opt/local/lib/libldastoolsal.3.dylib (compatibility version 4.0.0, current version 4.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)
	/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.0.0)

Users are more likely to have openssl installed, and it is much newer software than libwww so I expect openssl's implementation to be better. So ldas-tools should be instructed to use openssl, even if libmd5 is available. I did not see a configure argument to accomplish that. Possibly, you'll have to patch the configure script.