httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Stone <dan...@sfarc.net>
Subject Re: apache2 2.0.26 buildable?
Date Tue, 23 Oct 2001 09:26:56 GMT
On Mon, Oct 22, 2001 at 08:10:55PM +1000, Daniel Stone wrote:
> Hi guys -
> 
> Making all in mpm
> make[3]: Entering directory
> `/home/daniel/apache2-2.0.26/apache2-2.0.26/build-tree/apache2-2.0.26/server/mpm'
> make[3]: *** No rule to make target `all'.  Stop.
> make[3]: Leaving directory
> `/home/daniel/apache2-2.0.26/apache2-2.0.26/build-tree/apache2-2.0.26/server/mpm'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/home/daniel/apache2-2.0.26/apache2-2.0.26/build-tree/apache2-2.0.26/server'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/home/daniel/apache2-2.0.26/apache2-2.0.26/build-tree/apache2-2.0.26'
> make: *** [debian/stampdir/build] Error 2
> debuild: fatal error at line 322:
> dpkg-buildpackage failed!
> daniel@tsubasa:~/apache2-2.0.26/apache2-2.0.26% 

Hi,
Obviously the error was due to a missing --with-mpm=xxxxxx argument to
./configure. I just relied on the default behaviour being sane -
something that worked up until very recently. In this case, where it
breaks make'ing, shouldn't having no MPM be a fatal ./configure error?

Or, even better, shouldn't having a sane default, be the default?

-d

-- 
Daniel Stone						    <daniel@sfarc.net>
<Omnic> synx: good point, I wouldnt want to fondle Overfiend's man breasts

Mime
View raw message