www/apache2(2.0.48-2) is not started on FreeBSD 4.9. httpd is running. But root account only.(from ps output) It seems that 'fork' has gone wrong. 'APR_USE_PTHREAD_SERIALIZE' and 'libc_r.so.4' are difference.(see sentence end) Isn't 'thread' a problem? in 2.0.48-1(no problem) --------------------- > httpd -V Server version: Apache/2.0.48 Server built: Jan 13 2004 13:15:56 Server's Module Magic Number: 20020903:4 Architecture: 32-bit Server compiled with.... -D APACHE_MPM_DIR="server/mpm/prefork" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_FLOCK_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D HTTPD_ROOT="/usr/local" -D SUEXEC_BIN="/usr/local/sbin/suexec" -D DEFAULT_PIDLOG="/var/run/httpd.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_LOCKFILE="/var/run/accept.lock" -D DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="etc/apache2/mime.types" -D SERVER_CONFIG_FILE="etc/apache2/httpd.conf" > ldd /usr/local/sbin/httpd /usr/local/sbin/httpd: libz.so.2 => /usr/lib/libz.so.2 (0x280a9000) libssl.so.3 => /usr/lib/libssl.so.3 (0x280b7000) libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x280e7000) libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x281e4000) libexpat.so.4 => /usr/local/lib/libexpat.so.4 (0x281f6000) libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28213000) libm.so.2 => /usr/lib/libm.so.2 (0x2822f000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x2824b000) libc.so.4 => /usr/lib/libc.so.4 (0x28264000) --------------------- in 2.0.48-2(PROBLEM) --------------------- > httpd -V Server version: Apache/2.0.48 Server built: Jan 13 2004 19:30:37 Server's Module Magic Number: 20020903:4 Architecture: 32-bit Server compiled with.... -D APACHE_MPM_DIR="server/mpm/prefork" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_FLOCK_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D HTTPD_ROOT="/usr/local" -D SUEXEC_BIN="/usr/local/sbin/suexec" -D DEFAULT_PIDLOG="/var/run/httpd.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_LOCKFILE="/var/run/accept.lock" -D DEFAULT_ERRORLOG="/var/log/httpd-error.log" -D AP_TYPES_CONFIG_FILE="etc/apache2/mime.types" -D SERVER_CONFIG_FILE="etc/apache2/httpd.conf" > ldd /usr/local/sbin/httpd /usr/local/sbin/httpd: libz.so.2 => /usr/lib/libz.so.2 (0x280b0000) libssl.so.3 => /usr/lib/libssl.so.3 (0x280be000) libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x280ee000) libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x281ec000) libdb4.so.0 => /usr/local/lib/libdb4.so.0 (0x28200000) libexpat.so.4 => /usr/local/lib/libexpat.so.4 (0x28289000) libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x282a6000) libm.so.2 => /usr/lib/libm.so.2 (0x282c4000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x282e0000) libc_r.so.4 => /usr/lib/libc_r.so.4 (0x282f9000) --------------------- Fix: It may be what should just prepare 'WITHOUT_THREAD'. How-To-Repeat: It will reappear, if it probably tries on FreeBSD 4.9.
Responsible Changed From-To: freebsd-ports-bugs->clement It's mine. I'm currently working on a fix. removing ./patch-srclib:apr:build:apr_hints.m4 should be a workaround.
State Changed From-To: open->closed Workaround committed. Thanks for the notification !