Well, it seems it is all relatively simple - as most solutions tend to be. re: AddHandler message: the statement needed to be moved to within <IfModule mime_module> .... </IfModule>
Probably, my builds were working fine. I am running into other warnings, and I am wondering if there is a specific, recommended, or preferred order of LoadModule statements so that the built-in part of apache can be limited to the four (4) modules I kept seeing from the httpd -l output. My feeling now is the main file I will need to update for a distribution is httpd.conf and/or the conf/extra directory. Any advice in this line of thought is appreciated. The comment on having apr and apr-util separate from the apache build is something I shall be looking at. Regarding the recommendation to seperate apr and apache: I have no idea how apr and apr-util actually work, but I have read that 'recently' other projects have started to use apr. Would the proper approach be to configure and install apr and apr-util and then rerun the apache configure - so that apache knows to not use/install it's own apr and apr-util? Michael On Thu, Oct 15, 2009 at 1:01 PM, Michael Felt <mamf...@gmail.com> wrote: > OK. I'll see if that starts answering more questions than I am getting from > my "face-value" (or naive) approach to the infromation/hints coming from > binbuild.sh and configure --help. > > The mod with AddHandler is mod_mime - did a better search in the > documentation to find that. > > Just seems strange that "all" and "most" give nothing, and using only "so" > gives me a lot - or maybe too much? > =========== > mich...@x054:[/data/prj/httpd-2.2.14]cat config.nice > #! /bin/sh > # > # Created by configure > > "./configure" \ > "--enable-module=so" \ > "$@" > mich...@x054:[/data/prj/httpd-2.2.14]./httpd -l > Compiled in modules: > core.c > mod_authn_file.c > mod_authn_default.c > mod_authz_host.c > mod_authz_groupfile.c > mod_authz_user.c > mod_authz_default.c > mod_auth_basic.c > mod_include.c > mod_filter.c > mod_log_config.c > mod_env.c > mod_setenvif.c > mod_version.c > prefork.c > http_core.c > mod_mime.c > mod_status.c > mod_autoindex.c > mod_asis.c > mod_cgi.c > mod_negotiation.c > mod_dir.c > mod_actions.c > mod_userdir.c > mod_alias.c > mod_so.c > mich...@x054:[/data/prj/httpd-2.2.14]./httpd -t > lt-httpd: Syntax error on line 56 of /usr/local/apache2/conf/httpd.conf: > module cgi_module is built-in and can't be loaded > ======= > > > On Thu, Oct 15, 2009 at 12:21 PM, Graham Leggett <minf...@sharp.fm> wrote: > >> Michael Felt wrote: >> >> > mich...@x054:[/data/prj/httpd-2.2.14]./httpd -t >> > [Thu Oct 15 09:58:08 2009] [warn] module headers_module is already >> > loaded, skipping >> > Syntax error on line 69 of /usr/local/apache2/conf/httpd.conf: >> > Invalid command 'AddHandler', perhaps misspelled or defined by a module >> > not included in the server configuration >> > ===================================================================== >> > What mod needs to be static so "things" like AddHandler function >> properly? >> >> Look in the rpm spec file in build/rpm/httpd.spec.in, and find the >> ./configure line in there - use that as a starting point about the >> options to use. >> >> Obviously if any modules are left out, tweak accordingly. >> >> The only module that needs to be compiled statically (and it's compiled >> statically by default) is mod_so itself, the module that knows how load >> dynamic modules. >> >> Regards, >> Graham >> -- >> > >
