ID: 22259 Updated by: [EMAIL PROTECTED] Reported By: ikazdek at hotmail dot com -Status: Open +Status: Feedback Bug Type: Compile Failure Operating System: FreeBSD 4.7-STABLE PHP Version: 4.3.1 New Comment:
[From: ikazdek at hotmail dot com] For whatever flukey combination of reasons, the "fix" for this situation was to first ./configure WITHOUT ANY OPTIONS, then immediately ./configure with APXS and whatever other options you want to install. It now compiles every time when I do that. --- That's good to know and definately helps to track this down. Can you do the following: # rm config.cache # ./configure --with-apxs=<plusthepathtoapxs> # cp config.log config.log.apxs # rm config.cache # ./configure # cp config.log config.log.plain And send me the those config.log.* files. (Something is causing some tests to fail when you have --with-apxs there..comparing the config.logs I can see what it is.) Previous Comments: ------------------------------------------------------------------------ [2003-02-19 12:53:56] ikazdek at hotmail dot com [this should really stay] For whatever flukey combination of reasons, the "fix" for this situation was to first ./configure WITHOUT ANY OPTIONS, then immediately ./configure with APXS and whatever other options you want to install. It now compiles every time when I do that. [fluffy info] The compile would break only when we tried to use APXS, and it appeared to be related to stdarg.h and utime.h not being included. But simply compiling with them did not work either, it would break at other stages. If stdarg.h was cached by TSRM in the config, it would compile, if it wasn't it break. With APXS it would not be cached, without, it would. [this an all the other stuff should go I guess] Sniper - I understand why a couple messages were deleted now, but I think that they should have been snipped or that if your going to actually DELETE posts, something should be written into the bug reporting system to fire a note off to the original "bug" reporter to let them know WHY their post was deleted. After all, the person has taken the time to actually come here, post, and hopefully contribute to the advancement of PHP. If you just delete posts like that you rub just people wrong and they won't come back, at least if they are notified we can grow into better bug/issue reporters. So someone should consider adding a hack to quickly email a macroed response "Bugs.php.net post ID blah edited or deleted because: please to not post entire compile output" or "Not a support forum, please visit support.php.net" or whatever. I mean your no stranger to macros & that was my whole point. I HAD reviewed previous bug reports prior to opening this one and what I saw was a little annoying - your macroed fix or solution for everyone seems to always be "run the latest snapshot". Now while NOW, IN HERE you claim that recomendation is not for a fix, but to test, I've never seen that in your other posts. Maybe you should update your macro to suggest something along the same lines as the front page -- that the snap is not intended for production purposes and should only be compiled to test & report the status back here. Also, I wasn't aware that this also was relayed to usenet (Hi Mom), I can understand why you would want to keep the fluff down. ------------------------------------------------------------------------ [2003-02-18 21:00:14] ikazdek at hotmail dot com I've narrowed it down to apxs: --with-apxs=/usr/local/sbin/apxs Without the option to build it as a module, it will compile. ------------------------------------------------------------------------ [2003-02-17 21:18:32] [EMAIL PROTECTED] 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 ------------------------------------------------------------------------ [2003-02-17 18:27:39] ikazdek at hotmail dot com Making progress, but something is still goofy here... bash-2.05b# make CFLAGS=-DHAVE_STDARG_H Now crashes at what looks to be a little earlier: [snip-snip] In file included from /usr/local/src/php-4.3.1/ext/ctype/ctype.c:23: /usr/local/src/php-4.3.1/main/php.h:277: syntax error before `va_list' In file included from /usr/local/src/php-4.3.1/main/php.h:360, from /usr/local/src/php-4.3.1/ext/ctype/ctype.c:23: /usr/local/src/php-4.3.1/TSRM/tsrm_virtual_cwd.h:159: warning: `struct utimbuf' declared inside parameter list /usr/local/src/php-4.3.1/TSRM/tsrm_virtual_cwd.h:159: warning: its scope is only this definition or declaration, which is probably not what you want. *** Error code 1 Stop in /usr/local/src/php-4.3.1. ------------------------------------------------------------------------ [2003-02-17 18:03:38] ikazdek at hotmail dot com > Try grepping for stdarg in config.log bash-2.05b# cat config.log | grep -i stdarg configure:12921: checking for stdarg.h configure:80395: checking for stdarg.h configure:81463: checking for stdarg.h So would to appropriate answer for this problem be to make with CFLAGS=-DHAVE_STDARG_H ?? I'm really outside my realm of knowledge here... but I know there are others out there that have had this same problem in the past. ------------------------------------------------------------------------ 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/22259 -- Edit this bug report at http://bugs.php.net/?id=22259&edit=1
