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=20447>. 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=20447 Apache 2.0.46 fails to start ------- Additional Comments From [EMAIL PROTECTED] 2003-06-04 22:29 ------- can you show the output of ldd /local01/apache2b/lib/libapr-0.so.0 ldd /local01/apache2b/lib/libaprutil-0.so.0 ? I suspect that the final answer is going to be this: gcc code generation for libapr or libaprutil changed between 2.0.43 and 2.0.46, and the generated code now depends on libgcc, and your fix would be to edit Apache's bin/envvars to add the directory containing libgcc to the setting of LD_LIBRARY_PATH to test this theory, you'd need to get /local01/apache2b renamed to /local01/apache2 again, then edit /local01/apache2/bin/envvars... but first verify with ldd that /local01/apache2b/lib/libapr* is what depends on libgcc and in the future, some people have found this a useful way to test a new server without renaming the old directories always install apache-2.0.x into /usr/local/apache-2.0.x (or for you, /local01/apache-2.0.x) and use a symlink /usr/local/apache to the desired flavor so when you upgrade to 2.0.47, it gets installed in /usr/local/apache-2.0.47, and you can play with it there to make sure it works, and then change the symlink /usr/local/apache to point to /usr/local/apache-2.0.47 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
