From: gmbeard <gmbeard@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: apr: update to 1.7.2.
Date: Tue, 28 Mar 2023 21:37:46 +0200 [thread overview]
Message-ID: <20230328193746.CV3DqWCzAct8ltHphAuxDLKNKKu89EPW7Kl7VFKaHCA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42972@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
New comment by gmbeard on void-packages repository
https://github.com/void-linux/void-packages/pull/42972#issuecomment-1487493375
Comment:
I've managed to somewhat test this with apache in a x86\_64-glibc chroot. I manually bumped apr-util to `1.6.3`, and apache to `2.4.56` (looks like the existing apache template in the source tree has a dead distfile BTW).
Maybe not the most thorough of tests, but I can successfully start `httpd` with a default `httpd.conf` and get a dir listing page from `http://127.0.0.1:8080`
<details>
<summary>Output from <code>apachectl -V</code></summary>
```
Server version: Apache/2.4.56 (Unix)
Server built: Mar 25 2023 11:59:59
Server's Module Magic Number: 20120211:126
Server loaded: APR 1.7.2, APR-UTIL 1.6.3, PCRE 10.39 2021-10-29
Compiled using: APR 1.7.2, APR-UTIL 1.6.3, PCRE 10.39 2021-10-29
Architecture: 64-bit
Server MPM: event
threaded: yes (fixed thread count)
forked: yes (variable process count)
Server compiled with....
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_PROC_PTHREAD_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=256
-D HTTPD_ROOT=""
-D SUEXEC_BIN="/bin/suexec"
-D DEFAULT_PIDLOG="/var/run/httpd/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="/etc/apache/mime.types"
-D SERVER_CONFIG_FILE="/etc/apache/httpd.conf"
```
</details>
next prev parent reply other threads:[~2023-03-28 19:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 6:58 [PR PATCH] " gmbeard
2023-03-24 7:45 ` [PR PATCH] [Updated] " gmbeard
2023-03-24 8:28 ` gmbeard
2023-03-24 17:49 ` gmbeard
2023-03-25 8:55 ` gmbeard
2023-03-25 8:58 ` gmbeard
2023-03-25 11:34 ` gmbeard
2023-03-25 12:00 ` gmbeard
2023-03-28 19:37 ` gmbeard [this message]
2023-03-28 20:08 ` gmbeard
2023-04-05 4:29 ` gmbeard
2023-04-19 19:46 ` [PR REVIEW] " paper42
2023-04-19 19:46 ` paper42
2023-04-19 19:54 ` nekopsykose
2023-04-21 6:21 ` [PR PATCH] [Updated] " gmbeard
2023-04-21 6:23 ` [PR REVIEW] apr: update to 1.7.4 gmbeard
2023-04-21 6:26 ` gmbeard
2023-04-21 6:28 ` gmbeard
2023-04-21 6:44 ` [PR REVIEW] " gmbeard
2023-04-21 6:45 ` gmbeard
2023-07-21 1:55 ` github-actions
2023-08-05 1:48 ` [PR PATCH] [Closed]: " github-actions
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=20230328193746.CV3DqWCzAct8ltHphAuxDLKNKKu89EPW7Kl7VFKaHCA@z \
--to=gmbeard@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).