Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 78733 invoked by uid 500); 5 Aug 2003 06:17:19 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 78703 invoked from network); 5 Aug 2003 06:17:19 -0000 Received: from erato.logilune.com (HELO mail.logilune.com) (195.154.174.52) by daedalus.apache.org with SMTP; 5 Aug 2003 06:17:19 -0000 Received: from stason.org (localhost.logilune.com [127.0.0.1]) by mail.logilune.com (Postfix) with ESMTP id C68DF78E8C; Tue, 5 Aug 2003 08:17:28 +0200 (CEST) Message-ID: <3F2F4B5D.4090206@stason.org> Date: Tue, 05 Aug 2003 08:14:53 +0200 From: Stas Bekman Organization: Hope, Humanized User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030428 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joe Schaefer Cc: apreq-dev@httpd.apache.org Subject: Re: libapreq-1.2 release candidate 2 References: <3EE8129B.3040507@stason.org> <3F290183.5090308@stason.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Joe Schaefer wrote: > Stas Bekman writes: > > [...] > > >>I have resolved this issue. You couldn't reproduce it because you were >>running an old MakeMaker. I have explained the issue and provided a >>solution here: >>http://marc.theaimsgroup.com/?l=apreq-dev&m=105965131008577&w=2 > > > Thanks, Stas! However, the problem is that we actually rely on the > current behavior for platforms like OS-X, where people are encouraged > to install libapreq.so via './configure ...' prior to running the > perl-build of libapreq. I'm afraid your patch will break libapreq's > OS-X support for prior perls, and probably anywhere else that libapreq.so > (the C library) is installed before building Request.so and Cookie.so. Sure, it doesn't have to be the final patch. It just shows where the problem is and that you need the latest MM to reproduce it (I was confused before since I have too many perl builds and some of them had the old MM, while others the new one and I didn't think to point the blaming finger to MM). You probably know what's better solution is. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:stas@stason.org http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com