ID: 20497
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Bogus
Bug Type: Compile Failure
Operating System: solaris 8
PHP Version: 4.3.0RC1
New Comment:
sed is not the first or last tool in Solaris to be buggy as hell. And
it's not our problem if it is.
Previous Comments:
------------------------------------------------------------------------
[2003-01-13 11:33:27] [EMAIL PROTECTED]
When I upgraded the sed it worked, I think that SUN should .know about
this this should not be the case!!
sed functionality should be the same across the board.
-Ian
[EMAIL PROTECTED]
------------------------------------------------------------------------
[2003-01-13 11:29:26] [EMAIL PROTECTED]
I currently have the same problem on Solaris 8 (MU7),
apache-httpd 2.0.43 und php 4.3.0 (as dynamic module).
Shouldn't it work with the "sed" shipped with Solaris?
Maybe we should send SUN a bug report if something
is wrong with their implementation of "sed".
------------------------------------------------------------------------
[2003-01-07 13:35:25] [EMAIL PROTECTED]
After reading your comments, I installed GNU sed from sunfreeware.com.
PHP is now compiled properly. Thank you for this information.
------------------------------------------------------------------------
[2002-12-01 16:39:00] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
------------------------------------------------------------------------
[2002-11-19 12:20:34] [EMAIL PROTECTED]
Can you first check why the sed check didn't break the configure, from
config.log, look for something like this:
configure:1579: checking for working sed
(to 'fix' this problem, install GNU sed)
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/20497
--
Edit this bug report at http://bugs.php.net/?id=20497&edit=1
