Bug #17312 Updated: Build problem with GCC 3.1

ID: 17312 Updated by: mfischer@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: I've found this line through google: http://gcc.gnu.org/ml/gcc/2002-02/msg00965.html Previous Comments: ------------------------------------------------------------------------ [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 \ ------------------------------------------------------------------------ [2002-05-20 12:05:42] asautins@yahoo.com Building php 4.2.1 ( ./configure with no options ) using GCC 3.1 causes the following error: /usr/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. ext/mysql/libmysql/my_tempnam.o: In function `my_tempnam': /home/asautins/php4/ext/mysql/libmysql/my_tempnam.c:86: the use of tempnam' is dangerous, better use mkstemp' collect2: ld returned 1 exit status It looks like a warning, but php will not link. If I comment out the call to tempnam in my_temnam.c, it links correctly. Given that GCC 3.1 does not come as part of the standard distribution and I built it from source, that could be the problem, but I was able to reproduce on two separate instances. It would be nice to use php_open_temporary_file (main/php_open_temporary_file.c ) to avoid duplicating the effort, but it does not seem to be intended for use by modules. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17312&edit=1