I think the problem is only present if they have mawk installed under the name 'awk'. Magnus and I spent a fair bit if time trying things out with different awk implementations, as usual, with minimal feedback from anyone else, either in the internals community or outside of it.
How about having someone with mawk tweak the script so that it *does* work? There is nothing in there that really requires a specific awk implementation, and gawk certainly isn't installed on systems such as Solaris, where the dependency script works just fine. So, if you have mawk, get your finger out. --Wez. On 6/8/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: > Hello Andi, > > i forgot to mention one major problem. The current implementation of > extension dependency requires gnu-awk. If another awk implementation is > being used to generate php then the result is an immediate segfaulting > php binary. We should either make gawk checked by configure or rewrite > the exetension dependency by tables in the module struct so a dependent > extension doesn't get MINITed before its dependencies are initialized. > Probably we can go require way for 5.1 and have the other one done for > 5.2. > > Sunday, June 5, 2005, 7:18:26 PM, you wrote: > > > Hello Andi, > > > Saturday, June 4, 2005, 7:58:13 AM, you wrote: > > >> Hey, > > >> There have been a lot of questions and discussion regarding status of PHP > >> 5.1. > >> In the past few weeks, many have been fixing lots of bugs and PDO seems to > >> have reached a pretty stable state. > >> In parallel, a lot of work has been done offline by Andrei, Dmitry and > >> others, to enable Unicode support in PHP and the Zend Engine. > >> I believe it is time now to move 5.1 forward at a much faster pace. I'd > >> like to roll a beta of it towards the end of next week such as Thursday > >> (giving a chance for some last minute fixes), and then hopefully RC within > >> a week or two. > >> Once we RC PHP 5.1, we should branch it off to PHP_5_1 and make HEAD the > >> Unicode development stream (merging Unicode changes into HEAD). > > >> Hopefully, by going at this pace, we can have a pretty decent Unicode > >> version of PHP out there within a few months; and have PDO out there almost > >> immediately. > > > There are a few things i'd like to address before: > > > 1) return by reference at c-level. This is already taken care of by dmitry > > who is currently working on a better patch than mine. However i need this > > to finalizy ArrayAccess interface. And i need a bit of a time to experiment > > with the result and maybe others want to give their input as well. At the > > moment the problem is that it cannot deal with references at all but there > > is already coe out with 5.0 that used that issue. So here is just somewhat > > work and testing needed. > > > 2) PHP is all about the putting out text so nearly all objects created in > > PHP are meant to put something onto the generated pages. Thus i think i am > > not alone to suggest we put back the magic __toString function in place as > > we said when we dropped it's support from 5.0. Also it is very hard to > > explain why "echo $a . $obj" and "echo $a, $obj" output different things > > when one is an object. Both is pretty much against the spirit of PHP - > > easiness isn't it? > > > 3) Is 5.1 coming out without filtering? > > > 4) I still want the ifsetor operator since it is very helpfull and again > > simplifies a lot of things. > > > 5) tons of other stuff i menationed offline and in public - since i lost > > the energy in tracking all that issues i guess the work and time in those > > wasn't worse the effort and they can wait anyway :-) > > > best regards > > marcus > > > > > -- > Best regards, > Marcus mailto:[EMAIL PROTECTED] > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
