Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11576] Unable to start apache with event MPM on raspberry pi 3
Date: Sat, 05 Jan 2019 18:27:06 +0000	[thread overview]
Message-ID: <bug-11576-163-96ZtVpU379@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11576-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11576

--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
Apache is based on apr and apr has some configure runtime checks for some
features, e.g. epoll, failing for the cross compile.

Quick test with the following (buildroot) patch enables successful apache
startup again:

diff --git a/package/apr/apr.mk b/package/apr/apr.mk
index 58b1d86b28..8f29e57c59 100644
--- a/package/apr/apr.mk
+++ b/package/apr/apr.mk
@@ -26,7 +26,12 @@ APR_CONF_ENV = \
        ac_cv_sizeof_pid_t=4 \
        ac_cv_struct_rlimit=yes \
        ac_cv_o_nonblock_inherited=no \
-       apr_cv_mutex_recursive=yes
+       apr_cv_mutex_recursive=yes \
+       apr_cv_epoll=yes \
+       apr_cv_epoll_create1=yes \
+       apr_cv_dup3=yes \
+       apr_cv_sock_cloexec=yes \
+       apr_cv_accept4=yes
 APR_CONFIG_SCRIPTS = apr-1-config

 # Doesn't even try to guess when cross compiling

Tested with raspberrypi3_qt5we_defconfig and the following two
additional config options:

BR2_PACKAGE_APACHE=y
BR2_PACKAGE_APACHE_MPM_EVENT=y

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-01-05 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11576-163@https.bugs.busybox.net/>
2018-12-26 23:47 ` [Buildroot] [Bug 11576] Unable to start apache with event MPM on raspberry pi 3 bugzilla at busybox.net
2019-01-05 18:27 ` bugzilla at busybox.net [this message]
2019-01-17 22:14 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-11576-163-96ZtVpU379@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox