Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: domain of jorton@redhat.com designates
 66.187.233.31 as permitted sender)
Date: Fri, 26 Nov 2004 09:44:19 +0000
From: Joe Orton <jorton@redhat.com>
To: dev@httpd.apache.org
Subject: Re: PATCH: call aclocal for PCRE in buildconf
Message-ID: <20041126094419.GB15984@redhat.com>
Mail-Followup-To: dev@httpd.apache.org
References: <41A66890.5070801@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <41A66890.5070801@apache.org>
User-Agent: Mutt/1.4.1i

On Thu, Nov 25, 2004 at 03:19:44PM -0800, Brian Pane wrote:
> I found that the configure.in in recent releases of PCRE uses some 
> autoconf macros that won't work unless aclocal is called first to 
> produce a proper aclocal.m4: AC_PROG_LIBTOOL and AC_LIBTOOL_WIN32_DLL

Those macros should not be left in pcre/configure.in in a merge to a
newer PCRE, PCRE should not create and use its own copy of libtool, that
way lies disaster - configure.in would need to be adjusted to work as
the current build does, using the APR-supplied libtool script.

So it shouldn't be necessary to run aclocal.

joe