Summary: | --enable-static is not available in apache's configure file and don't work | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Yannick LE NY <yannick.leny> |
Component: | Build | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | REOPENED --- | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.2.10 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Yannick LE NY
2008-10-16 06:58:23 UTC
--enable-static / --enable-shared was removed when the build system was refactored from scratch in httpd 2.0. It is no longer present. Yo can now use --enable-modules / --enable-mods-shared to specify which modules should be build static or dynamic. *** Bug 46025 has been marked as a duplicate of this bug. *** (In reply to comment #2) > *** Bug 46025 has been marked as a duplicate of this bug. *** >--enable-static / --enable-shared was removed when the build system was >refactored from scratch in httpd 2.0. It is no longer present. Yo can now use >--enable-modules / --enable-mods-shared to specify which modules should be >build static or dynamic. Thank you for this answer. Please add this VERY USEFUL information in http://httpd.apache.org/docs/2.2/en/upgrading.html. Strange because the command-line --enable-static and --enable-shared works fine with Apache 2.0.59 and not in Apache 2.2.10. if this option is not available now, please add this change in the apache 2.2.x changes or changelog file and explain why this option is removed and write that there are new options that replace the old options. Please propose your deisred documentation patch or at least bullet points (in ***one*** bug incident, just use this one) for all the flags that now "do nothing" or have changed. As pointed out these ***never did anything*** from httpd 2.0.0 through today. The culprit of your confusion is *autoconf*. This will affect all the various packages you build, one by one as the maintainers migrate and roll out new packages. 2.0.63, and 2.2.9-.10 are affected here. Autoconf had a strict rule that unrecognized flags should not cause failure. The maintainers in the 2nd-to-the-most-recent release of autoconf have changed this underlying assumption. So all unrecognized flags scream out where they were silently ignored before. |