Bug #17312 Updated: Build problem with GCC 3.1

ID: 17312 Updated by: asautins@php.net Reported By: asautins@yahoo.com Status: Open Bug Type: MySQL related Operating System: Redhat 7.2 PHP Version: 4.2.1 New Comment: Is this something that could be caught when ./configure is run? My concern is that ./configure checks for tempnam successfully eventhough it will not link. However, since this seems to be the behavior of AC_CHECK_FUNCS there might not be anything to do. Previous Comments: ------------------------------------------------------------------------ [2002-05-22 15:41:14] mfischer@php.net Even better this one http://gcc.gnu.org/ml/gcc/2002-02/msg01071.html (one of the Follow-Ups) ------------------------------------------------------------------------ [2002-05-22 15:39:57] mfischer@php.net I've found this line through google: http://gcc.gnu.org/ml/gcc/2002-02/msg00965.html ------------------------------------------------------------------------ [2002-05-22 15:32:59] asautins@php.net To me it looks like the linker has trouble with it somehow. Compiles OK, but fails in linking with the 'unhandled FORM value: 14' error. Again, it looks as if the routines in my_tempnam.c are not referenced anywhere in the extension, so to me it looks as if it would be safe to remove the source file. ------------------------------------------------------------------------ [2002-05-22 15:19:20] mfischer@php.net Does this mean by chance the gcc 3.1 treats this as an error what used to be a warning only in 2.9x ? ------------------------------------------------------------------------ [2002-05-22 12:31:04] asautins@php.net It seems that the functions in my_tempnam.c are not used. If I removed my_tempnam.c from ext/mysql/config.m4 php builds and seems to run correctly. config.m4 53c53 < libmysql/my_delete.c libmysql/my_tempnam.c libmysql/my_open.c libmysql/mf_casecnv.c libmysql/my_read.c \ --- > libmysql/my_delete.c libmysql/my_open.c libmysql/mf_casecnv.c libmysql/my_read.c \ ------------------------------------------------------------------------ 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/17312 -- Edit this bug report at http://bugs.php.net/?id=17312&edit=1