Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3E804344.9070802@attglobal.net>
Date: Tue, 25 Mar 2003 06:53:40 -0500
From: Jeff Trawick <trawick@attglobal.net>
Reply-To: trawick@attglobal.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: [PATCH] build problem with stable and older libtool
References: <5.2.0.9.2.20030324213331.038880d8@pop3.rowe-clan.net>
In-Reply-To: <5.2.0.9.2.20030324213331.038880d8@pop3.rowe-clan.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

This has been in the STATUS file a while anyway.  That makes 3 +1s, 
since there was already my vote:

     * get out-of-tree APR builds to work for libtool 1.3.x users
       buildconf: r1.32
       +1: trawick

(Note that the diff is different from r1.32 with APACHE_2_0_BRANCH since 
the code has to be added to APACHE_2_0_BRANCH instead of modified.  The 
only difference was the comment...  I kept the comment the same as in 
HEAD so that APACHE_2_0_BRANCH doesn't have unique code.)

William A. Rowe, Jr. wrote:
> I'll see your +1 and raise you +1... I thought the patch was required
> to build with apr out of tree - if everyone is going to be bit on 
> libtool 1.3 releases let's get it in there now, and into the .45 release.
> 
> Bill
> 
> At 06:16 PM 3/24/2003, Greg Ames wrote:
> 
>>I'm trying to get WROWE_2_0_45_RC1 going on daedalus and got:
>>
>>/home/gregames/httpd-2.0.45-wr1/shlibtool: /home/gregames/httpd-2.0.45-wr1/shlibtool: No such file or directory
>>*** Error code 127
>>
>>...when make tried to build mod_access (the first module we build as a DSO). This is a symptom of using libtool 1.3 without having ltconfig and ltmain.sh accessable to httpd's configure.  Looks like we need 1.29 and 1.31 in the tag.
>>That's what this patch does, in addition to tweaking the comment a little to make it more obvious why this code is important.
>>
>>This patch solves the problem.  Can I get some +1's on committing it to the stable branch?
>>
>>Thanks,
>>Greg
>>
>>Index: buildconf