#22184 [Opn->Fbk]: Compile fails looking for m4sugar

ID: 22184 Updated by: iliaa@php.net Reported By: marcus@synchromedia.co.uk -Status: Open +Status: Feedback Bug Type: Compile Failure Operating System: OpenBSD 3.1-stable PHP Version: 4CVS-2003-02-12 (stable) New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [2003-02-13 08:56:47] marcus@synchromedia.co.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 07:48:29] 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 05:41:38] marcus@synchromedia.co.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-12 10:37:41] 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-12 04:39:41] marcus@synchromedia.co.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? ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=22184&edit=1