Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:7764
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 11 Feb 2004 19:09:33 +0200 (EET)
Reply-To: Jani Taskinen <sniper@iki.fi>
To: Pierre-Alain Joye <paj@pearfr.org>
Cc: internals@lists.php.net
In-Reply-To: <20040211172218.2208cfed@localhost.localdomain>
Message-ID: <Pine.LNX.4.53.0402111824400.32432@ybpnyubfg.ybpnyqbznva>
References: <5.1.0.14.2.20040211140521.0641ebe0@localhost>
 <5.1.0.14.2.20040211140605.04419790@127.0.0.1> <20040211131837.75ac4ef0@localhost.localdomain>
 <Pine.LNX.4.53.0402111806420.32432@ybpnyubfg.ybpnyqbznva>
 <20040211172218.2208cfed@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Fwd: Re: dl() problem
From: sniper@iki.fi (Jani Taskinen)

On Wed, 11 Feb 2004, Pierre-Alain Joye wrote:
>Jani Taskinen <sniper@iki.fi> wrote:
>
>>     Our codebase is much larger than any other plus we 'misuse'
>>     the auto* tools. :) Feel free to bring the stuff up-to-date so
>>     we actually COULD update to latest libtool/autoconf, etc.
>>     I looked at this once and decided it wasn't worth the effort..
>
>I used the auto* tools as a sample of another similar case :). Note I'm
>not an expert of auto* as you seems to be, and only wondering why it
>does not work. Is it another good reason to delay the php5 release and
>fix it? It seems we are all busy as hell, and many "bugs" are left due
>to this fact.

    Delay it another year? Then maybe. :)
    I'm sure not gonna spend my precious time with this non-issue
    as the versions we rely on work fine.

>What do you mean by 'misuse'? maybe some informations/tips can help to
>get fixes?

    Sascha propably can explain better, I remember that the auto*/libtool
    developers once said we use the tools wrong or something like that. :)

>>     (autoconf > 2.13 is slow too. And the generated configure is
>>     REALLY slow.
>
>lol who cares? Do you generate a configure every hour?

    Yes, I generate it quite often. And my machine isn't the fastest
    in the world so for me it's an issue if generating configure 
    takes very long time..here are quick'n'dirty benchmarks:
    
    Latest auto*/libtool:
    
      # time ./buildconf
      real    1m28.287s
      user    1m22.080s
      sys     0m5.710s

    "Old" auto*/libtool:
    
      # time ./buildconf
      real    0m18.772s
      user    0m15.750s
      sys     0m5.350s

    Running ./configure only takes about 20s more with new tools,
    so that's not so big issue.

>>  Not to forget the fact that the versions I tested are also buggy in
>>  some cases, can't remember right now in what way and too busy to
>>  actually test again) 
>
>Could help if you remember these issues :)

    I have no time nor interest in testing it all again..
    
    --Jani