ID:               15959
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Feedback
+Status:           No Feedback
 Bug Type:         Compile Failure
 Operating System: FreeBSD 4.4-STABLE
 PHP Version:      4.0CVS-2002-03-08
 New Comment:

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".


Previous Comments:
------------------------------------------------------------------------

[2002-04-23 00:16:09] [EMAIL PROTECTED]

I can not reproduce this with CVS HEAD or 4.2.0..
(using autoconf 2.53)

Is this strictly Freebsd /bin/sh related?


------------------------------------------------------------------------

[2002-03-13 22:02:21] [EMAIL PROTECTED]

Well, I just tried the patch listed in that mailing list. It fixes the
problem with AC_CONFIG_COMMANDS as advertised. Unfortunately PHP is
still producing empty case/esac statements in ./configure. It would be
great if someone more familiar with auto* could find out what rule is
causing this.

php: 4.0CVS2002-03-13
autoconf: 2.53
freebsd: 4.5-STABLE



------------------------------------------------------------------------

[2002-03-13 20:36:42] [EMAIL PROTECTED]

This looks like the way to fix it:

http://www.geocrawler.com/lists/3/GNU/402/0/7718080/

------------------------------------------------------------------------

[2002-03-08 13:00:25] [EMAIL PROTECTED]

FreeBSD /bin/sh doesn't like empty case/esac statements.
One such gets created in config.status:1472. 

I *think* I've seen a mail about empty case statements being patched in

one of the GNU autotools, so this should probably be considered an
auto* 
bug, but I can't for the life of me find where it was. svn-dev@ or 
freebsd-questions@ probably.



------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=15959&edit=1

Reply via email to