From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <199812012212.RAA24007@devsys.jaguNET.com>
Subject: Re: [PATCH] Configuration (3/4): APACI Makefile for src/Configure
To: new-httpd@apache.org
Date: Tue, 1 Dec 1998 17:12:15 -0500 (EST)
In-Reply-To: <199812012158.QAA20836@devsys.jaguNET.com> from "Jim Jagielski"
 at Dec 1, 98 04:58:12 pm
Content-Type: text
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

> > > Randy Terbush wrote:
> > > > 
> > > > I'm not sure what platform I would consider having the dumbest
> > > > shell. I seem to run into many shell problems on BSDI and HPUX. Anyone 
> > > > know if a good base level V7 shell test for APACI?
> > > 
> > > I use A/UX's 'sh' which isn't a true V7 shell, but backwards enough
> > > and limited enough that it easily barfs on large scripts (even GNU's).
> > > That plus my dog-eared copy of "The UNIX Programming Environment" are
> > > kinda my guides :)
> > 
> > Can you confirm or deny problems with that shell in the APACI
> > configure?
> > 

So far, simply running './configure' with some various '--enable-module's
result in a working build sequence. However, building results in
the below type lines:

 gcc -c  -I../os/unix -I../include -DAUX3 -D_POSIX_SOURCE `../apaci` util.c

The `../../apaci` is new but is part of the normal APACI build where it
overrides paths...

Since some stuff will be committed soon, I'll hold off on the detailed
walkthrough until then.
-- 
===========================================================================
   Jim Jagielski   |||   jim@jaguNET.com   |||   http://www.jaguNET.com/
            "That's no ordinary rabbit... that's the most foul,
            cruel and bad-tempered rodent you ever laid eyes on"