Forum OpenACS Q&A: Re: When building nsopenssl-2.1a I get the "OpenSSL was not compiled with thread support!" error
I guess OpenSSL was REALLY not compiled with thread support. But how do I enable thread support?
read the INSTALL file in the openssl source directory and/or
type there ./Configure --help
You should be able to install openssl in the aolserver tree, make sure you can load shared libraries from there, and recompile ns_openssl with that source-tree/installation.
commenting out the warning message is not a solution.
PS: we are not using nsopenssl.
This time I compiled and installed OpenSSL before compiling and installing nsopenssl
# compile and install OpenSSL
# compile and install nsopenssl
gmake install INST=/home/aol3
When running building nsopenssl I did not get the"OpenSSL was not compiled with thread support!" error!
But I do run into other issues now. When I run AOLserver, all the http pages work just fine. But when I hit the first https page, I get the following error message:
"*** glibc detected *** double free or corruption (!prev): 0x08ff3548 ***
and the AOLserver process dies.
I guess I'm one step closer to solving this problem. Thanks for your help Gustaf!
why you are building still an aolserver 3.*? I would expect, that the problem disappears, when you use aolserver 4.*.
However, if you have to go the hard way, i would recommend that you post the problem into the aolserver mailing list (with exact version numbers of tcl, aolserver, openssl, glibc, your operating system, architecture, etc.)
I'm running ACS-3.4.9, and for a while I've been getting the nsopenssl errors mentioned above. So I took the task of recompiling AOLserver-3.3.1+ad13 to see if the errors disappeared.
I now believe the errors occur because OpenSSL is not compiled with thread support on the box. The person that originally installed everything on the box didn't compile the AOLserver, he just copied the executables, so he had no way of knowing what was going on.
We have a lot of in house code written for this ACS system and migrating to OpenACS would be HARD work (https://openacs.org/forums/message-view?message_id=250524). I'll probably end up doing this some day.
Before posting to the AOLserver mailing list I'll try running ACS 3 on AOLserver 4. I have not tried this because of the ad13 part in AOLserver-3.3.1+ad13 but who knows, maybe I'll be extremely lucky and get it working =). If you know this just won't work, please let me know.
Using AOLserver 4.0.x or 4.5.x will probably work for ACS 3.4.9, but you might have to tweak a few things. AFAIK, all the ad13 features that you should need to run ACS were eventually forward-ported to AOLserver 4.0.x. I don't know whether they kept the exact same API or not in all cases though, particularly for the character set stuff.
I don't think 4.0.x includes the ad13 Tcl bytecode cache, which might be a performance issue if your site is very busy. Then again, some very large sites (like Gustaf's) are running on OpenACS + AOLserver 4.x, and they don't seem to have missed it.