httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20447] - Apache 2.0.46 fails to start
Date Wed, 04 Jun 2003 21:25:10 GMT
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 trawick@apache.org  2003-06-04 21:25 -------
I guess that /local01/apache2/bin/httpd is 2.0.46 and
/local01/apache2b/bin/httpd is 2.0.43?

libgcc_s.so.1 isn't a dependency of either httpd, so if the lack of
libgcc_s.so.1 is keeping httpd to start, then it must be a dependency of some
library that 2.0.46's httpd references but 2.0.43's httpd does not.

Such libraries could be libssl or libcrypto.

       libssl.so.0.9.6 =>       /usr/local/ssl/lib/libs
       libcrypto.so.0.9.6 =>    /usr/local/ssl/lib/libc

Does either of those reference libgcc_s.so.1?

Apparently you built 2.0.46 with different features (mod_ssl) than 2.0.43, since
the libraries they depend on are different.  Perhaps that is the change that has
triggered this problem?  Perhaps you didn't notice that some crypto library
needed libgcc_s.so.1 before because your 2.0.43 httpd didn't need it.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message