#33354 [Csd]: I recieve a warning on ./configure for no apparent reason

ID: 33354 User updated by: webmaster at pro-g dot co dot uk Reported By: webmaster at pro-g dot co dot uk Status: Closed Bug Type: Compile Failure Operating System: freeBSD 5.4-RELEASE PHP Version: 5.0.4 New Comment: Right... so what can I do? I require php5 on the server within the next week, but do not need your added features for 5.1... Previous Comments: ------------------------------------------------------------------------ [2005-06-16 15:13:22] sniper@php.net Let's close this bug report as the configure is fixed. 5.1 is gonna be the next PHP 5 release. But it might not be yet stable enough for production use. (as seen with the compile failure with ext/date which was added recently :) ------------------------------------------------------------------------ [2005-06-16 14:56:41] webmaster at pro-g dot co dot uk I successfully ./configured with my additional extentions etc, but then went to actually compile and recieved syntax errors, as seen in the following log (scroll down): http://nopaste.php-q.net/141421 Perhaps my GCC is out of date? ------------------------------------------------------------------------ [2005-06-16 14:44:50] webmaster at pro-g dot co dot uk This appears to have worked (with both the --with-apxs2= switch too). Well done! I assume it is safe to use this version in production? ------------------------------------------------------------------------ [2005-06-16 12:45:09] sniper@php.net This warning comes from all those crypt tests: "cast to pointer from integer of different size" Propably some 64bit issue. Please try the latest snapshot: http://snaps.php.net/php5-latest.tar.gz ------------------------------------------------------------------------ [2005-06-15 20:05:57] webmaster at pro-g dot co dot uk Thanks for replying. The config.log for the './configure' command alone can be found here: http://nopaste.php-q.net/141291 ------------------------------------------------------------------------ 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/33354 -- Edit this bug report at http://bugs.php.net/?id=33354&edit=1