Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14249 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41379 invoked by uid 1010); 31 Dec 2004 05:23:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41189 invoked from network); 31 Dec 2004 05:23:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Dec 2004 05:23:25 -0000 X-Host-Fingerprint: 213.243.153.36 smtp3.pp.htv.fi Linux 2.4/2.6 Received: from ([213.243.153.36:43282] helo=smtp3.pp.htv.fi) by pb1.pair.com (ecelerity HEAD (r3992M)) with SMTP id F8/13-10264-C42E4D14 for ; Fri, 31 Dec 2004 00:23:25 -0500 Received: from localhost.localdomain (cs78146149.pp.htv.fi [62.78.146.149]) by smtp3.pp.htv.fi (Postfix) with ESMTP id 1CB6D27AE58; Fri, 31 Dec 2004 07:23:22 +0200 (EET) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id iBV5NLbT000748; Fri, 31 Dec 2004 07:23:21 +0200 Received: from localhost (jani@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) with ESMTP id iBV5NKBT000744; Fri, 31 Dec 2004 07:23:20 +0200 X-Authentication-Warning: localhost.localdomain: jani owned process doing -bs Date: Fri, 31 Dec 2004 07:23:20 +0200 (EET) Reply-To: Jani Taskinen To: Rasmus Lerdorf Cc: internals@lists.php.net In-Reply-To: <41D46CE5.2050101@lerdorf.com> Message-ID: References: <41D46CE5.2050101@lerdorf.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [PHP-DEV] generate ltmain.sh? From: sniper@iki.fi (Jani Taskinen) On Thu, 30 Dec 2004, Rasmus Lerdorf wrote: > We have ltmain.sh in our cvs. It is from an old libtool and not compatible > with newer libtools. Specifically the shared_ext is not defined so we end up > generating libraries without the .so extension. > A simple rm ltmain.sh && libtoolize --force fixes it, but is there anything > stopping us from either shipping a newer ltmain.sh (it seems to be backward > compatible) or not shipping one at all and doing a libtoolize --force from > buildconf? Actually we should always be using the generated libtool, whatever libtool you might have installed. The reason to bundle libtool is to have one variable out of the equation with different build environments, IMO. Exactly how do you get the problem with shared_ext..? --Jani