Re: Apache 2_0_31 is now rolled (take 2)
Victor J. Orlikowski wrote: > > Ugh. Behind on mail. > > My fault; needed it for cadaver for testing... ;) > Why do I feel like I just entered an episode of 6 Feet Under? :) -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson
RE: Apache 2_0_31 is now rolled (take 2)
My apologies. The context was to provide a semi-humorous reply to the breakage I caused Jeff by installing Expat on the AIX box we use. Been a while since the mail, been a while since I posted last. Grrr. ;) Victor -- Victor J. Orlikowski | The Wall is Down, But the Threat Remains! == [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED]
RE: Apache 2_0_31 is now rolled (take 2)
> From: Victor J. Orlikowski [mailto:[EMAIL PROTECTED]] > Ugh. Behind on mail. > > My fault; needed it for cadaver for testing... ;) Victor: You need a little context on your mail. I don't know about others, but I have no idea what you are replying to. Joshua.
Re: Apache 2_0_31 is now rolled (take 2)
Ugh. Behind on mail. My fault; needed it for cadaver for testing... ;) Victor -- Victor J. Orlikowski | The Wall is Down, But the Threat Remains! == [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED]
Re: Apache 2_0_31 is now rolled (take 2)
Jeff Trawick <[EMAIL PROTECTED]> writes: > Jeff Trawick <[EMAIL PROTECTED]> writes: > > > I'm still struggling with the tarball on AIX. I think it is just a > > matter of cleaning up libtool 1.3 droplets so that a fresh buildconf > > does what it is supposed to do. > > That and, for me, working around the fact that "somebody" installed an > expat RPM on the AIX box I use and apparently the shared library it > installs doesn't have the same name that apr-util wants to load, > resulting in a load failure for libexpat. no, the real explanation is: for testing this tarball I did the binbuild on one machine and installed it on a different machine; I didn't have the expat RPM installed on the target machine the fact is that all along I've been using a separate expat on my build machine and didn't realize it :( (that could explain a hack I had to put in the build somewhere; dunno yet) > Time to add --with-expat=srclib/apr-util/xml/our-freaking-copy-of-expat > to binbuild.sh and try again :( After doing that, everything is humming. +1 for beta based on AIX testing of something built via binbuild... sending a mix of requests, no unexpected error log messages, no high CPU or storage I'll commit the binbuild.sh change to 2.0.32-dev. It could get challenging to build a reasonable binary distribution otherwise. Special instructions for AIX (may apply to other platforms where libtool-in-tarball is uncool): 1) make sure autoconf 2.13 and libtool 1.4.2 are found first 2) unpack tarball and cd to top-level directory 3) remove all occurrences of ltconfig and ltmain.sh in the source tree 4) if you have an expat installation already, you may want to apply the patch below 5) ./buildconf 6) CC=xlc_r build/binbuild.sh (or invoke configure yourself) patch for overriding the expat selection: Index: build/binbuild.sh === RCS file: /home/cvs/httpd-2.0/build/binbuild.sh,v retrieving revision 1.33 diff -u -r1.33 binbuild.sh --- build/binbuild.sh 7 Jan 2002 16:03:25 - 1.33 +++ build/binbuild.sh 2 Feb 2002 17:25:54 - @@ -9,9 +9,10 @@ OS=`./srclib/apr/build/config.guess` BUILD_DIR="`pwd`/bindist" DEFAULT_DIR="/usr/local/apache2" -CONFIGPARAM="--with-layout=BinaryDistribution --prefix=$BUILD_DIR --enable-mods-shared=most" APDIR=`pwd` APDIR=`basename $APDIR` +APFULLDIR=`pwd` +CONFIGPARAM="--with-layout=BinaryDistribution --prefix=$BUILD_DIR +--enable-mods-shared=most --with-expat=$APFULLDIR/srclib/apr-util/xml/expat" VER=`echo $APDIR |sed s/httpd-//` TAR="`srclib/apr/build/PrintPath tar`" GTAR="`srclib/apr/build/PrintPath gtar`" -- Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...
Re: Apache 2_0_31 is now rolled (take 2)
Compiles and serves pages on Windows. Need to spend a bit more time to see if it is beta quality. Bill > the NW patch is in there. > the non-crap tarballs are in the /dist directory. > > > > who would have thought making a tar ball would be so hard. > ..Ian >
Re: Apache 2_0_31 is now rolled (take 2)
Ian Holsman wrote: > > the NW patch is in there. > the non-crap tarballs are in the /dist directory. > > who would have thought making a tar ball would be so hard. > ..Ian The version I got from ~jerenkrantz yesterday PM has been running live on daedalus since Saturday, 02-Feb-2002 07:58:29 PST. And yes, graceful restart works fine. It's got the save_input patch, and a patch to keep the parent alive if the kernel hits the system wide fd limit. Greg
Re: Apache 2_0_31 is now rolled (take 2)
Jeff Trawick <[EMAIL PROTECTED]> writes: > I'm still struggling with the tarball on AIX. I think it is just a > matter of cleaning up libtool 1.3 droplets so that a fresh buildconf > does what it is supposed to do. That and, for me, working around the fact that "somebody" installed an expat RPM on the AIX box I use and apparently the shared library it installs doesn't have the same name that apr-util wants to load, resulting in a load failure for libexpat. Time to add --with-expat=srclib/apr-util/xml/our-freaking-copy-of-expat to binbuild.sh and try again :( -- Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...
Re: Apache 2_0_31 is now rolled (take 2)
Ian Holsman <[EMAIL PROTECTED]> writes: > the NW patch is in there. > the non-crap tarballs are in the /dist directory. +1 for FreeBSD 3.4... I unpacked it, did binbuild, did the binbuild installation, and hammered* it over local LAN with 200,000 requests (mix of CGI, / to drive lots of wrowe code, invalid URLs), throwing in a few graceful restarts to make it interesting *given the rather modest characteristics of my FreeBSD box, perhaps "hammered" isn't the right term :) I'm still struggling with the tarball on AIX. I think it is just a matter of cleaning up libtool 1.3 droplets so that a fresh buildconf does what it is supposed to do. The symptoms of my binbuild failures are consistent with the use of some libtool other than 1.4.2, and I've been testing Apache 2.0 HEAD builds every several hours on AIX, with multiple compilers and multiple build flavors, without hitting any problems that aren't resolved in 2.0.31. The only recent breakage was Bill's proxy breakage (fixed prior to 2.0.31) and the APR_OS_DEFAULT breakage (introduced after 2.0.31). --/-- There's no magic solution for now w.r.t. creating a tarball that works everywhere since some of our platforms have conflicting libtool version requirements. All we can hope to accomplish currently is a) the source tarball works as-is on a reasonable number of platforms (yeah, somebody may end up unhappy, but I promise not to scream if it won't work as-is on a platform I care about) b) people familiar with platform problems can work around them (e.g., wipe clean and do buildconf) to do a valid binary build when the time comes c) we write down any work-arounds in a common place so that end users can replicate the procedures -- Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...
Re: Apache 2_0_31 is now rolled (take 2)
On Fri, Feb 01, 2002 at 04:46:58PM -0800, Ian Holsman wrote: > the NW patch is in there. > the non-crap tarballs are in the /dist directory. > > > > who would have thought making a tar ball would be so hard. No kidding. It'll be easier next time. After initially thinking there was a problem with graceful restarts on prefork, it just appears to takes about 6 seconds to complete a graceful restart cycle on my Linux 2.4.8 box. In the meantime, ps lists the children processes as defunct (which scared me off at first). But, after about 6 seconds, httpd starts serving again (incl. queued requests). Anyway, this delay looks defendable. I think this delay is acceptable, so I'm officially +1 on the 2.0.31 tarball for beta from: http://www.apache.org/dist/httpd/httpd-2_0_31-alpha.tar.gz Enjoy. -- justin
