Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Sender: trawick@rdu88-250-182.nc.rr.com
To: dev@httpd.apache.org
Subject: Re: Query: bugs 8712 and 10156/NOW 10235 as well.
References: <1027270064.1540.5.camel@lerlaptop.lerctr.org>
	<m3adohgkbi.fsf@rdu88-250-182.nc.rr.com>
	<1027528982.406.24.camel@lerlaptop.iadfw.net>
From: Jeff Trawick <trawick@attglobal.net>
Date: 24 Jul 2002 13:34:24 -0400
In-Reply-To: <1027528982.406.24.camel@lerlaptop.iadfw.net>
Message-ID: <m3sn2981y7.fsf@rdu88-250-182.nc.rr.com>
Lines: 44
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Larry Rosenman <ler@lerctr.org> writes:

> > > 10156

I will plan to commit your patch in the next 24 hours.  e-mail me
directly if this doesn't happen.

> > > 10235

> > What is the exact failure with --enable-mods-shared=all?  Are the
> > modules built?  Do they load?

> 
> I thought I included full scripts.... I can make a shell account
> available.....

I see the failure to load mod_access now.  I got frustrated by all the
terminal control sequences at the end of your attachment.

Is ap_get_remove_host exported from httpd?  nm on httpd should be able
to tell.  You may need to axe the libtool --silent option (LTFLAGS=' '
./configure ...), see how httpd and your DSOs are linked, and compare
it with what a DSO build of Apache 1.3.  Maybe your level of libtool
is broken for your platform, maybe there is something that Apache
needs to do special.

> > What exactly is the IPv6 failure?  Did everything build?  Was there a
> > run-time failure?

> Basically, on this platform for now you need to ignore the IPv6 stuff,
> and not use it. (there is an API, but no protocol stack). 

It is the same with many Linux boxes on which Apache works fine
without disabling the IPv6 support.  We don't choose to disable IPv6
in the build if the API is there.

Does Apache fail without --disable-ipv6?  Is there a symptom we can
check for at configure time?  We do check for certain broken APIs and
disable it in that situation.  Maybe there is another symptom we
should check for.

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...