Re: undesired modules loading

2012-08-19 Thread Rainer Jung
On 19.08.2012 00:20, Roy T. Fielding wrote: On Aug 18, 2012, at 1:45 PM, Rainer Jung wrote: Yes, before 2.4.0 we introduced exactly this difference. All modules that were build get a LoadModule line in the installed config, but most are commented out. I don't have the list of modles active

Re: undesired modules loading

2012-08-19 Thread Stefan Fritsch
On Sunday 19 August 2012, Roy T. Fielding wrote: Partial answer: the current semantics of maintainer-mode is (per configure help): Turn on debugging and compile time warnings and load all compiled modules Umm, WTF? Why? One reason was to make it easier for httpd developers to run

undesired modules loading

2012-08-18 Thread Roy T. Fielding
I built 2.4.3 with the options ./configure \ --prefix=$tdir \ --with-apr=$adir \ --with-apr-util=$adir \ --without-ssl \ --without-crypto \ --disable-cache \ --without-distcache \

Re: undesired modules loading

2012-08-18 Thread Rainer Jung
Hi Roy, On 18.08.2012 22:07, Roy T. Fielding wrote: I built 2.4.3 with the options ./configure \ --prefix=$tdir \ --with-apr=$adir \ --with-apr-util=$adir \ --without-ssl \ --without-crypto \ --disable-cache \

Re: undesired modules loading

2012-08-18 Thread Jim Jagielski
It's '--enable-maintainer-mode' which introduces this behavior. When being built for mere mortals, we are much nicer as far as which modules are built and loaded by default Maybe --enable-maintainer-mode should be renamed --enable-developer-mode On Aug 18, 2012, at 4:07 PM, Roy T. Fielding

Re: undesired modules loading

2012-08-18 Thread Roy T. Fielding
On Aug 18, 2012, at 1:45 PM, Rainer Jung wrote: Yes, before 2.4.0 we introduced exactly this difference. All modules that were build get a LoadModule line in the installed config, but most are commented out. I don't have the list of modles active by default at hand though. Ah, okay. At