Re: 4.3 RC1 - mysql compile warning

On Thu, 21 Nov 2002 07:31:17 +0100 (CET), derick@php.net (Derick Rethans) wrote: >On Wed, 20 Nov 2002, Brad Bulger wrote: > >> compile warning: >> >> ext/mysql/libmysql/my_tempnam.lo: In function `my_tempnam': >> /usr/local/src/php-4.3.0RC1/ext/mysql/libmysql/my_tempnam.c(.text+0x5e): warning >> : tempnam() possibly used unsafely; consider using mkstemp() [...] >The MySQL guys implemented it in a safe way, so it's really not a >problem. Just ignore it :) Which makes this a gcc problem. Also, look at it: "possibly used unsafely" Whenever you log into a computer, you can possibly use it unsafely. It's just unfortunate, that this message is the last one, that is displayed after compiling PHP, so that people remember it and it contains the word 'unsafe'. If you make 2>errs and grep errs for 'from incompatible pointer type', you get warnings, which fall into the 'possible segfault' category (if you stretch that the way this warning is stretched, I'd say "possible remote root exploit"). -- Melvyn Sopacua <?php include_once("not_reflecting_employers_views.txt"; ?>