Bug 46024 - --enable-static is not available in apache's configure file and don't work
Summary: --enable-static is not available in apache's configure file and don't work
Status: REOPENED
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Build (show other bugs)
Version: 2.2.10
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
: 46025 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-10-16 06:58 UTC by Yannick LE NY
Modified: 2008-10-16 09:52 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yannick LE NY 2008-10-16 06:58:23 UTC
I found nothing about this problem in Apache bugzilla.

When I do :
./configure --help
i can not see the option :
--enable-static

I found nothing about that this option was removed in
http://www.apache.org/dist/httpd/CHANGES_2.0
or
http://www.apache.org/dist/httpd/CHANGES_2.2

Please can you add --enable-static as option
in configure file when I do ./configure --help or
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.

Use ./buildconf in httpd-2.2.10 folder and next do configure don't help  

Error message when I do ./configure :
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type:
checking for chosen layout... Apache
checking for working mkdir -p... yes
checking build system type... config.sub: missing argument
Try `config.sub --help' for more information.
configure: error: /bin/sh build/config.sub   failed
./script.03_apache_httpd.linux32: line 65: --enable-static: command not found
make: *** Pas de cibles spécifiées et aucun makefile n'a été trouvé. Arrêt.

Environment :
Apache 2.2.10
Redhat Linux ES4.0
GNU Make 3.80
autoconf (GNU Autoconf) 2.59
automake (GNU automake) 1.9.2
Comment 1 Ruediger Pluem 2008-10-16 07:19:17 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.
Comment 2 Ruediger Pluem 2008-10-16 07:19:21 UTC
*** Bug 46025 has been marked as a duplicate of this bug. ***
Comment 3 Yannick LE NY 2008-10-16 07:28:56 UTC
(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.
 

Comment 4 William A. Rowe Jr. 2008-10-16 09:52:02 UTC
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.