kmra...@rockwellcollins.com wrote on Thu, Jun 21, 2012 at 13:13:46 -0500: > Daniel Shahaf <danie...@elego.de> wrote on 06/21/2012 12:57:46 PM: > > > > > Also, specifying --without-apxs does not correctly disable > building > > > > > mod_dav_svn and mod_dontdothat. The build fails with a missing > > > httpd.h, > > > > > error, so I pointed it to my local build of httpd as a workaround. > > > > > > > > > > > > > httpd 2.2 or 2.4? > > > > > > I pointed it to 2.2.22 as a workaround, but originally I was trying to > > > build without mod_dav_svn or mod_dontdothat (passing --without-apxs) > > > That just fails if you do not have httpd-devel installed... > > > > > > > We'll have to fix that then. I'm not sure (without checking logs) > > whether it's one of the 1.7.x bugs I'd mentioned. > > The svn logs mention this was supposedly fixed for 1.7.4, but not for me. > What should I look for in the configure log? >
--with-apxs controls the configure variables BUILD_APACHE_RULE and INSTALL_APACHE_RULE used by configure.ac and several Makefile.in variables (via AC_SUBST() calls) --- see build/ac-macros/apache.m4. These then propagate to Makefile. The previous fixes were at the (build/generator/*.py, build/generator/*/makefile.ezt, build-outputs.mk) level. > > > > I remember fixing an issue with mod_dontdothat and such --- and also > > > > nominting it for 1.7.x backport --- if there is still an issue here > > > > I could look... > > > > > > > > (Well, rather, "add it to my list". Quite busy this and next week) > > > > > > > > > Another very *minor* thing I noticed is that the sqlite3 error > > > > > during the build still references the old sqlite3 naming > > > > > format and references a http:// URL that is no longer valid. > > > > > > > > Which error? The one in build/ac-macros/sqlite.m4? Line number > please? > > > > > > Just (on a machine with old sqlite3 installed): > > > mv sqlite-almagamation foo > > > ./configure > > > > > > > Why didn't you just say "yes" ? Could you send a patch to the file I > named? > > Because you didn't ask a yes or no question :) > Actually I did (the 2nd one). Thanks for clearing that up, and sorry for the misunderstanding.. > I didn't see that specific error mentioned in the file you pointed at, so > I was hopeful the actual error message would help someone who has > seen an m4 file before. (I certainly haven't mucked with them before) > > Kevin R. >
