On 02/19/12 23:28, Steve Bennett wrote: >> For the record (in case someone finds this via a web search): I think >> there's something odd about the openssl detection. I had built openssl >> without the "shared" option (so I only had the shared libraries). But > > Building without "shared" meant you only had the shared libraries??
Oops; I meant I only had "static" libraries. Sorry for the confusion. >> even with "configure --static" (in fossil), I ran into linking problems. >> Building openssl with the "shared" option made those problems go away. I >> haven't looked into it more closely, as the workaround is trivial, and I >> think most people will have the shared libraries laying around anyway. > With the fix I sent earlier, does openssl detection work properly? It started working once I had built the dynamic OpenSSL libraries. That's what I thought felt odd -- the detection seemed to fail to find the OpenSSL static libs, even though "--static" was passed. [---] > How about forget about static linking and just use dynamic linking? Oh, I got dynamic linking working yesterday; that's not a problem -- but as I wrote in my other mail, I'm specifically looking to dynamically link (more specifically: with OpenSSL). (I stress that this is not something I'm doing to torture myself, I'm using a network of several Solaris systems, and I want to be able to build one fossil binary and move it around; so there's a practical reason for my battle with static builds on Solaris). > Can we address the dynamic configure/build issues, and then possibly > revisit static linking? The dynamic linking works, but unfortunately on these particular systems I want static linking. :) -- Kind regards, Jan Danielsson _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
