On 2014-09-11T16:09:42 -0400 Eric Rubin-Smith <eas....@gmail.com> wrote: > > I skimmed through the configure code. Looks like you need to have > the subdir and file 'openssl/ssl.h' beneath the dir you specify, and > the subdir and files 'lib/libssl.so' and 'lib/libcrypto.so' beneath the > dir you specify. Furthermore, one of those libraries has to provide > the symbol "SSL_new". > > My (very quick and possibly wrong) read of the code is that those are > exactly the "pass criteria" for deciding that SSL is supported on the > build box using the dir your specify.
Think that may be partly wrong, as that'd mean that if I specified /usr, then the following would have to exist: /usr/openssl/ssl.h ... and that's obviously not true of any of the other platforms upon which I've built fossil. I do have (where → indicates a symlink): /usr/include/openssl/ssl.h /usr/lib/libssl.so → /usr/lib/libssl.so.6 /usr/lib/libssl.so.6 /usr/lib/libcrypto.so → /lib/libcrypto.so.6 /lib/libcrypto.so.6 /usr/local/include/openssl/ssl.h /usr/local/lib/libcrypto.so → /usr/local/lib/libcrypto.so.8 /usr/local/lib/libcrypto.so.8 /usr/local/lib/libssl.so → /usr/local/lib/libssl.so.8 /usr/local/lib/libssl.so.8 The /usr/lib/*.so libraries are stripped, so doesn't appear to have any symbols, but the /usr/local/lib/*.so libraries aren't, and the ssl library definitely contains SSL_new. M _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
