#21896 [Bgs]: Compile warning for Mysql
ID: 21896 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Bogus Bug Type: Compile Failure Operating System: RH linux 7.2 PHP Version: 4.3.0 New Comment: It's not PHP problem if you have used a broken compiler, such as the RH provided GCC 2.96 is. http://gcc.gnu.org/gcc-2.96.html Previous Comments: [2003-02-01 08:03:01] [EMAIL PROTECTED] Dear It was not BOGUS dont you get that PHP has some issues while compiling with GCC 2.96 2731 or vis-versa. [2003-01-27 09:11:28] [EMAIL PROTECTED] As it wasn't any bug in PHP -> bogus. (the warning can be ignored since tempnam() is not used 'dangerously' there) [2003-01-27 06:50:43] [EMAIL PROTECTED] Thanks [EMAIL PROTECTED] you were right the culprit in our case was GCC version 2.96 2731 , What i did 1. removed said version and installed GCC 3.0.2 20010905 2. Made a symbolic link to gcc3 as gcc 3. Did used my old confgiurtion script for php (ofcource after /make clean ;rm -rf config.cache; ) 4. Rest all went fine just the error which you said could be ingnored Still persist --Start "/hdc6/apache/php-4.3.0/ext/mysql/libmysql/my_tempnam.c:103: the use of `tempnam' is dangerous, better use `mkstemp'" ---End Will you please explain me why this erorr . Now my all apps are running fine and with God speed.The phpinfo is fine. Thanks for the valuable input [2003-01-27 02:49:00] [EMAIL PROTECTED] Do the same again, but use './configure' instead. [2003-01-27 02:34:04] [EMAIL PROTECTED] So you say it didn't work for 2 first times, but the 3rd one worked? That would really mean there are some problems in your system rather than anything wrong with PHP.. 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/21896 -- Edit this bug report at http://bugs.php.net/?id=21896&edit=1
#21896 [Bgs]: Compile warning for Mysql
ID: 21896 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Bogus Bug Type: Compile Failure Operating System: RH linux 7.2 PHP Version: 4.3.0 New Comment: Dear It was not BOGUS dont you get that PHP has some issues while compiling with GCC 2.96 2731 or vis-versa. Previous Comments: [2003-01-27 09:11:28] [EMAIL PROTECTED] As it wasn't any bug in PHP -> bogus. (the warning can be ignored since tempnam() is not used 'dangerously' there) [2003-01-27 06:50:43] [EMAIL PROTECTED] Thanks [EMAIL PROTECTED] you were right the culprit in our case was GCC version 2.96 2731 , What i did 1. removed said version and installed GCC 3.0.2 20010905 2. Made a symbolic link to gcc3 as gcc 3. Did used my old confgiurtion script for php (ofcource after /make clean ;rm -rf config.cache; ) 4. Rest all went fine just the error which you said could be ingnored Still persist --Start "/hdc6/apache/php-4.3.0/ext/mysql/libmysql/my_tempnam.c:103: the use of `tempnam' is dangerous, better use `mkstemp'" ---End Will you please explain me why this erorr . Now my all apps are running fine and with God speed.The phpinfo is fine. Thanks for the valuable input [2003-01-27 02:49:00] [EMAIL PROTECTED] Do the same again, but use './configure' instead. [2003-01-27 02:34:04] [EMAIL PROTECTED] So you say it didn't work for 2 first times, but the 3rd one worked? That would really mean there are some problems in your system rather than anything wrong with PHP.. [2003-01-27 02:32:42] [EMAIL PROTECTED] with configuration the output is # make clean # rm config.cache # ./configure --disable-all --disable-cgi # make ---Start o Zend/zend_stack.lo Zend/zend_variables.lo Zend/zend.lo Zend/zend_API.lo Zend/ zend_extensions.lo Zend/zend_hash.lo Zend/zend_list.lo Zend/zend_indent.lo Zend/ zend_builtin_functions.lo Zend/zend_sprintf.lo Zend/zend_ini.lo Zend/zend_qsort. lo Zend/zend_multibyte.lo Zend/zend_execute.lo sapi/cli/php_cli.lo sapi/cli/geto pt.lo main/internal_functions_cli.lo -lcrypt -lresolv -lm -ldl -lnsl -lcrypt -o sapi/cli/php End This completes but what about support'S 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/21896 -- Edit this bug report at http://bugs.php.net/?id=21896&edit=1
