Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Sender: trawick@rdu163-40-092.nc.rr.com
To: dev@httpd.apache.org
Subject: Re: I'd like to release 1.3.24...
References: <200202021503.KAA22846@devsys.jaguNET.com>
From: Jeff Trawick <trawick@attglobal.net>
Date: 02 Feb 2002 12:32:25 -0500
In-Reply-To: <200202021503.KAA22846@devsys.jaguNET.com>
Message-ID: <m3heozeqmu.fsf@rdu163-40-092.nc.rr.com>
Lines: 31
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Jim Jagielski <jim@jaguNET.com> writes:

> I'd like for us to consider releasing 1.3.24 specifically for the Solaris
> pthread fix. I offer to be RM. I'll update STATUS for voting and comments.

+1 from me :(

By the way...  would a shell expert such as yourself know how to catch
a bad exit from apache-1.3/src/Configure in the apache-1.3/configure
code below and make sure that configure exits with a bad status too?

if [ "x$quiet" = "xyes" ]; then
    (cd $src; ./Configure ${vflag} -file Configuration.apaci >/dev/null);
else
    (cd $src; ./Configure ${vflag} -file Configuration.apaci |\
     sed -e '/^Using config file:.*/d' \
         -e "s:Makefile in :Makefile in $src\\/:" \
         -e "s:Makefile\$:Makefile in $src:")
fi

Use case:

Some dumbass like me sets CFLAGS to something bogus and runs
configure...  the bad CFLAGS causes the compiler sanity check to fail
but configure exits with status 0 and a script that does the configure
will keep on trucking until the build fails at a more confusing place.

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