Organization: Freelancer X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
Organization: Freelancer X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 11 Feb 2004 18:10:40 +0200 (EET) Jani Taskinen <[EMAIL PROTECTED]> 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. What do you mean by 'misuse'? maybe some informations/tips can help to get fixes? I can give it a try in 2 or 3 weeks, not before and absolutely no warranty. I'm only a poor user of these tools ;). > Just use the snapshots if your auto* tools don't work. :) I use CVS for now ;) > (autoconf > 2.13 is slow too. And the generated configure is > REALLY slow. lol who cares? Do you generate a configure every hour? > 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 :) pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
