DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8993>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8993 openssl library location(s) are hardcoded in configure script ------- Additional Comments From [EMAIL PROTECTED] 2003-04-24 17:42 ------- Hmmm, I think I have been running into this problem since some time ago, I recognize the script code, I remember spending an ungodly amount of time hacking that file to get my Apache 2.0.x running on Red Hat 7.2, the problem as I figured it one day, way that libssl.so.0.9.7 and libcrypto.so.0.9.7 had to be copped into /lib before Apache would compile (yes, with --enable-ssl --with- ssl=/usr/local/ssl) with openssl. Those locations are definatly hard coded into that file. And if the *.so files do not match with your version of openssl, it will error out. That is why it worked just fine with Slackware, but not with Red Hat, different versions and some luck. The error is produced later on in that file, as the build process tries to run "openssl version", the lib versions do not match, "openssl version" returns an error, and the build process stop. I'm not sure if this is an Apache error, or a combination of distribution+Apache+openssl type of error. I do not believe openssl requires you to put those libs in /lib... It has been a while; I wish I could be clearer. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
