ID: 22074 Comment by: hson at ludd dot luth dot se Reported By: lhecking at nmrc dot ucc dot ie Status: Closed Bug Type: Compile Failure Operating System: Solaris PHP Version: 4.3.0 New Comment:
I'm running Solaris8 on x86, all the latest patches. When compiling 4.3.1 I also encountered this problem. But the problem is not sh(1) or sed(1), but both... I had to install gnu sed and set SHELL='/bin/bash' when compiling to get it to work. Previous Comments: ------------------------------------------------------------------------ [2003-03-09 13:31:26] reinpost at win dot tue dot nl I have this problem (for the first time) with 4.3.1 and sed is not involved. THe culprit is /bin/sh. Using make LIBTOOL='bash libtool' SHELL=`which bash` solves it for me. ------------------------------------------------------------------------ [2003-02-10 11:26:52] [EMAIL PROTECTED] libtool in CVS is now 1.4.3. Snapshots might not get it right yet as I can not update libtool on snaps.php.net but this will be fixed soon too. ------------------------------------------------------------------------ [2003-02-05 10:29:47] lhecking at nmrc dot ucc dot ie Many users, including myself, have report compile failures on Solaris due to the limitations of the native sed tool. All reporters were pointed to GNU sed, but part of the problem is that the sed test in php's configure is broken and declares even the native Solaris sed "working". Solution: upgrade to libtool 1.4.3, which includes a much better test for sed. I.e. re-run aclocal, and copy ltmain.sh over from PREFIX/share/libtool. If this particular problem is the only reason of existence for PHP_PROG_SED, this macro can safely be removed after upgrading to libtool 1.4.3. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=22074&edit=1
