Bug 44025 - Apache 2.2.6 fails to configure on OpenBSD 4.1
Summary: Apache 2.2.6 fails to configure on OpenBSD 4.1
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Build (show other bugs)
Version: 2.2.6
Hardware: PC OpenBSD
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2007-12-05 11:29 UTC by D.J.
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description D.J. 2007-12-05 11:29:13 UTC
I'm attempting to install Apache v2.2.6 on OpenBSD v4.1.  Unfortunately, I'm met
with the following when trying to run the configure script:

*** BEGIN COMMAND LINE CAPTURE***

phoenix# ./configure --enable-so
checking for chosen layout... Apache
checking for working mkdir -p... yes
checking build system type... i386-unknown-openbsd4.1
checking host system type... i386-unknown-openbsd4.1
checking target system type... i386-unknown-openbsd4.1

Configuring Apache Portable Runtime library ...

checking for APR... sed: "./srclib/apr/include/apr_version.h": No such
file or directory
configure: error: failed to find major version of bundled APR
phoenix#
Comment 1 D.J. 2007-12-06 11:54:24 UTC
(In reply to comment #0)

Well, I found a workaround, but I'm not sure it's a resolution.  If I run...

./configure --enable-so --with-included-apr

...configure doesn't puke anymore.
Comment 2 Joe Orton 2008-02-11 03:47:55 UTC
This is curious, is this still reproducible with 2.2.8?
Comment 3 yary h 2008-02-23 17:49:52 UTC
OpenBSD comes with a patched version of Apache 1.3, which most likely means an
old version of the APR as well. I suppose they don't have the APR header files
in the right place (or at all?)- and even then it wouldn't be the APR Apache 2.x
needs.

Perhaps this could be fixed by setting configure's "default" to
"--with-included-apr" when on OpenBSD?

I'm not an expert on OpenBSD or Apache, so take the above as a pointer, not a
definitive answer.
Comment 4 William A. Rowe Jr. 2018-11-07 21:08:45 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.