On Thu, April 13, 2006 5:04 pm, Richard Lynch wrote: Still slogging away at this.
> ./build/shtool path $PHP_AUTOCONF > test ! -x "./build/shtool path $PHP_AUTOCONF" Apparently, I'm the exception to this: http://www.zend.com/lists/php-dev/200503/msg00414.html "And finally: Common users should NEVER EVER run buildconf." What's that old saying? Every pro started as an amatuer I don't claim to understand the implications of the thread, nor Sebastion's problems where, but I gotta weigh that if a stock FreeBSD can't use it, maybe it needs fixin'... >From what little I do understand, if I've managed to set $PHP_AUTOCONF to point to a working autoconf, I don't think I ought to get told off for not having it set... :-) I'm about to try to just disable that check and move on with life -- But surely a FreeBSD user shouldn't have to do that. The workaround implied in the thread linked above, of making symlinks... I'm thinking maybe "root" user can just symlink to /usr/local/bin/autoconf and call it done. But does every C source code developer who wants to add an extension to PHP really need to run as "root"? Rasmus made this look SOOOO easy in his talk :-) -- Like Music? http://l-i-e.com/artists.htm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
