#21029 [Com]: "make" crashed because my_tempnam.c (not really)

ID: 21029 Comment by: ibj at earthlink dot net Reported By: php at 5en1 dot com Status: Open Bug Type: Documentation problem Operating System: all PHP Version: 4.3.0 New Comment: I think the mysql code has been fixed. I was getting the same compiler error, but after downloading the source for the latest version of mysql (3.23.55) and pointing the config --with-mysql option at the unpacked mysql source, it compiled without a hitch. The build was for PHP4.3.1 on RedHat Linux 7.2 (2.4.18 kernel). Hope this helps! Previous Comments: ------------------------------------------------------------------------ [2003-01-29 23:08:53] philip@php.net It's finally time we make a FAQ out of this. Ilia's comments provide enough to make a good start so this is being reclassified as an open documentation problem. ------------------------------------------------------------------------ [2003-01-29 18:32:58] msopacua@php.net No - it doesn't (trust me). But please ask about this at php-install@php.net. ------------------------------------------------------------------------ [2003-01-29 18:09:02] djlopez at gmx dot de Hi, on FreeBSD 4.4 I'm doing "make" and the warning appears, but it HALTS on this warning, and no php binary is made!! ------------------------------------------------------------------------ [2002-12-16 12:47:39] iliaa@php.net Because the warning is not in the PHP code, but rather then mysql library. Until the developers of that library (MySQL Developers) decide that this issue is something worth fixing, we PHP developers can do nothing but wait. There may be reasons why they chose this function over the 'safer' alternative. No matter the compiler warning messages will never prevent successful compilation, they are WARNING not ERRORs, that is unless you've made your compiler 'die' on warnings. ------------------------------------------------------------------------ [2002-12-16 12:29:12] php at 5en1 dot com why did it not continue de compiling so ??? however, it's easy to fix this "warning", why do you wont do it ???????? ------------------------------------------------------------------------ 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/21029 -- Edit this bug report at http://bugs.php.net/?id=21029&edit=1