On Wed Aug 25 17:17:21 2010, [email protected] wrote: > It appears that this happens (unconditionally?) in the configure > script: > > checking for library containing MD5_Init... -lcrypto > checking for library containing MD5Init... no
> (I'm looking at > https://buildd.debian.org/fetch.cgi?pkg=isc-dhcp;ver=4.1.1-P1- > 9;arch=amd64;stamp=1279996807 > if you want to look at the whole build log) > > Is there some magical undocumented flag I can pass configure to get it > to > not do this? Why isn't the supplied MD5 code (dst/md5.h and friends) > sufficient? My memory is that we added the search for -lcrypto for linking with Solaris systems. I'm not sure why we're searching for the MD5_Init function, there may not have been a better symbol to search for (it could be from the initial Autoconf work converting the old build environment to the new auto* tools - the engineer might not have known why the Solaris ./configure clauses chose to include -lcrypto and guessed). In 4.1 I'm pretty sure we do use the MD5_ functions from the dst library, but then in 4.2 we're now using the lib/isc library's 'isc_md5_init()' and family, so we should remove this for 4.2 and look at why we were doing this in 4.1. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
