You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Daniel Stone <da...@sfarc.net> on 2001/10/22 12:10:55 UTC

apache2 2.0.26 buildable?

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% 

Seems a little odd. I'm using CVS, with the APACHE_2_0_26 tag as of
about 15min ago. The ./configure and make calls are pretty stock
standard:

AP2_CONFARGS =  --enable-layout=Debian --enable-so \
                --with-program-name=apache2 --enable-speling=shared \
                --enable-rewrite=shared --enable-cgid=shared \
                --enable-vhost-alias=shared --enable-info=shared \
                --enable-suexec=shared --enable-ssl=shared \
                --enable-unique-id=shared --enable-usertrack=shared \
                --enable-expires=shared --enable-cern-meta=shared \
                --enable-mime-magic=shared --enable-headers=shared \
                --enable-auth-anon=shared --enable-proxy=shared

AP2_CONFLAGS = -I/usr/include/xmltok

        cd $(B) && ./buildconf
        cd $(B) && CFLAGS="$(AP2_CONFLAGS)" ./configure $(AP2_CONFARGS)
        cd $(B) && $(MAKE)

(where $(B) is the build tree).

Any clues? Should I be tracking HEAD instead of APACHE_2_0_26 for the package?

Thanks!
:) d

-- 
Daniel Stone						    <da...@sfarc.net>
hi; i?m in frqnce qnd I CQNNOT FIGURE OUT THE KEYBOQRDS HERE: Its
reqlly zeird; but the keys qre in different plqces111 gottq go; tq tq
-- Aaron Lehmann, emailing crackmonkey-l from France

Re: apache2 2.0.26 buildable?

Posted by Jeff Trawick <tr...@attglobal.net>.
Daniel Stone <da...@sfarc.net> writes:

> 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?

prefork is supposed to be the default; I just did 

  make extraclean
  cvs update
  ./buildconf
  ./configure
  make

on Linux; prefork was selected as desired and it built fine, so

1) something about your system that confuses us
*or*
2) temporary breakage to Apache which has since been fixed

Either way, it might help if you could try again with the latest
sources.  If it fails,

what do you have instead of this line?

  checking which MPM to use... prefork

what is in your config.nice?

Thanks,
-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...

Re: apache2 2.0.26 buildable?

Posted by Daniel Stone <da...@sfarc.net>.
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						    <da...@sfarc.net>
<Omnic> synx: good point, I wouldnt want to fondle Overfiend's man breasts