On Wed, 2012-12-12 at 14:22 +0000, Keith W wrote: > Hi all > > We are having problems building proton-c on our dev boxes (Red Hat > Enterprise Linux Server release 5.3 (Tikanga)). I've done a git > bisect and discovered that it was Andrew's commit last Wednesday (rev > 1417553) that has introduced/exposed the issue. Before that point, we > could build without this issue.
It seems that the link process is not resolving all the symbols it needs. That change introduces checking to be sure that all symbols used by the link are actually present somewhere. The simplest explanation is that openssl is not being linked in the final link, but is being detected enough to activate the code using it. Could you run "make VERBOSE=1" and post the final link line (only). As a workaround you can turn this checking off with "cmake -DENABLE_UNDEFINED_ERROR=OFF". However if the warning is good then you shouldn't actually be able to run code with ssl connections (unless you link the final executable with openssl, which isn't really necessary). Another useful datapoint would be to build with the above flag and then post the results of "ldd libqpid-proton.so". Andrew
