php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #22184 Compile fails looking for m4sugar
Submitted: 2003-02-12 04:39 UTC Modified: 2003-02-18 04:18 UTC
From: marcus at synchromedia dot co dot uk Assigned:
Status: Not a bug Package: Compile Failure
PHP Version: 4CVS-2003-02-12 (stable) OS: OpenBSD 3.1-stable
Private report: No CVE-ID: None
View Developer Edit
 [2003-02-12 04:39 UTC] marcus at synchromedia dot co dot uk 
I'm having trouble compiling current 4.3.1 CVS. I've done a completely fresh checkout. I'm using a minimal configure of:

./configure --with-apxs=/usr/sbin/apxs

I'm using autoconf 2.53, automake 1.6.3, libtool 1.4.3 and m4 1.4. It's using the stock OpenBSD Apache version which is 1.3.24.

The same setup compiles 4.3.0-release with no difficulty.

Configure goes ok, make fails with the following error:

/usr/local/bin/gm4: m4sugar/m4sugar.m4: No such file or directory
m4_changecom()
m4_init()
m4_define([b4_actions], 
[[  case 4:
#line 208 "/usr/local/src/php4/ext/standard/parsedate.y"

<many pages of source code dumped here>

m4_divert_push(0)mv y.tab.c /usr/local/src/php4/ext/standard/parsedate.c
mv: y.tab.c: No such file or directory
*** Error code 1

A minor note, probably unrelated - when I do CVS updates, I get lots of errors reported saying files are in the way in the Zend and TSRM directories. Something I'm missing?

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-02-12 10:37 UTC] iliaa@php.net 
Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip

Try getting a fresh tree (not updating the old one) the error you are seeing is probably due to corrupted CVS sources.
 [2003-02-13 05:41 UTC] marcus at synchromedia dot co dot uk 
When I said I was using a fresh checkout, I did mean completely fresh - I deleted everything and checked out an entirely new tree, so I'd already eliminated that.

That snapshot compiles ok.

I just checked out another brand-new tree and I get the same error as described originally, so the difference is somewhere between the current CVS and that snapshot.

I did notice that the snapshot builds quite differently to the CVS version. for example, ./buildconf just outputs one line, and the build includes the creation of a whole load of symbolic links that I've not noticed before.
 [2003-02-13 07:48 UTC] iliaa@php.net 
The difference betweent the snapshots & the CVS is that with snapshots buildconf has already been run the the configure script has been built using the individual m4 files. 
Since you are having problem with the CVS I must conclude that the problem lies with one of the system utilities used during the buildconf process.
What versions of autoconf & libtool are you using?
 [2003-02-13 08:56 UTC] marcus at synchromedia dot co dot uk 
From my original posting: I'm using autoconf 2.53, automake 1.6.3, libtool 1.4.3 and m4 1.4. Just for good measure, I recompiled and reinstalled all of them. Any other programs I should check?

Is the release version built like a snapshot? It does do a buildconf like the CVS version, but I don't get this error with it.
 [2003-02-13 09:14 UTC] iliaa@php.net 
Since the configure and the .h files are already built running buildconf does nothing beyond checking that they exists and moving on. Autoconf 2.53 is not recommended for building php configure, if possible try upgrading to a later version (2.57 is the latest) or downgrade to 2.13, which is known to work properly.
 [2003-02-13 10:31 UTC] marcus at synchromedia dot co dot uk 
I downgraded to autoconf 2.13 (and buildconf no longer complains about it), but I'm still getting the same error.
 [2003-02-13 12:20 UTC] sniper@php.net 
What is the EXACT output of 'm4 --version' ??
And did you get m4,libtool,autoconf from www.gnu.org ?
And compiled yourself? (m4 needs to be first..)
 [2003-02-18 04:17 UTC] marcus at synchromedia dot co dot uk 
After much frustration, I have now recompiled absolutely everything: kernel, whole OS, all the appropriate dev tools (m4, autoconf etc), pulled a fresh CVS copy of PHP, and now it finally compiles. I don't know where the problem was, but wherever it was, it's now gone away. As I don't know if the fix was done in PHP or my system, this should probably be marked as bogus.
 [2003-02-18 04:18 UTC] marcus at synchromedia dot co dot uk 
Marking as bogus.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sun Sep 07 03:00:01 2025 UTC