Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:14251
Return-Path: <chip@force-elite.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 76362 invoked by uid 1010); 31 Dec 2004 05:51:03 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 74241 invoked from network); 31 Dec 2004 05:50:06 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 31 Dec 2004 05:50:06 -0000
X-Host-Fingerprint: 216.255.199.145 force-elite.com Linux 2.4/2.6
Received: from ([216.255.199.145:37319] helo=utopia.in.force-elite.com)
	by pb1.pair.com (ecelerity HEAD (r3992M)) with SMTP
	id 84/44-10264-B88E4D14 for <internals@lists.php.net>; Fri, 31 Dec 2004 00:50:04 -0500
X-AuthUser: chip@force-elite.com
Received: from [10.0.0.101] (10.0.0.101:49407)
	by utopia.in.force-elite.com with [XMail 1.17 (Linux/Ix86) ESMTP Server]
	id <S8B95C> for <internals@lists.php.net> from <chip@force-elite.com>;
	Thu, 30 Dec 2004 21:49:55 -0800
Message-ID: <41D4E883.5080003@force-elite.com>
Date: Thu, 30 Dec 2004 21:49:55 -0800
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jani Taskinen <sniper@iki.fi>
CC: internals@lists.php.net
References: <41D46CE5.2050101@lerdorf.com> <Pine.LNX.4.61.0412310720320.423@ybpnyubfg.ybpnyqbznva>
In-Reply-To: <Pine.LNX.4.61.0412310720320.423@ybpnyubfg.ybpnyqbznva>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] generate ltmain.sh?
From: chip@force-elite.com (Paul Querna)

Jani Taskinen wrote:
> 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..?
> 

run buildconf from a cvs snapshot, and on some platforms (eg FreebSD 5) 
it will make install will install 'libphp4' instead of 'libphp4.so'

-Paul