#21029 [Bgs->Opn]: "make" crashed because my_tempnam.c (not really)

ID: 21029 Updated by: philip@php.net -Summary: "make" crashed because my_tempnam.c Reported By: php@5en1.com -Status: Bogus +Status: Open -Bug Type: Compile Failure +Bug Type: Documentation problem -Operating System: red hat 7.2 +Operating System: all -PHP Version: 4.3.0RC3 +PHP Version: 4.3.0 New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [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@gmx.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@5en1.com why did it not continue de compiling so ??? however, it's easy to fix this "warning", why do you wont do it ???????? ------------------------------------------------------------------------ [2002-12-15 16:10:19] sniper@php.net Not a PHP bug. (gcc should not consider that 'error' as fatal, previous versions just output a warning about 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