ID: 17312
Comment by: renjin@starhub.net.sg
Reported By: asautins@yahoo.com
Status: No Feedback
Bug Type: MySQL related
Operating System: Redhat 7.2
PHP Version: 4.2.1
New Comment:
OS: linux mandrake 2.4.18
PHP: 4.3.0
i got the problem... again...
my 4.2.3 make nicely.
my 4.3.0 screw up with this error
--------
ext/mysql/libmysql/my_tempnam.o: In function `my_tempnam':
/home/install/tmp/php-4.3.0/ext/mysql/libmysql/my_tempnam.c:103: the
use of tempnam' is dangerous, better use mkstemp'
--------
can anyone tell me which files in my
php-4.3.0/ext/mysql/
should i replace to re-fix the problem, please?
thanks
Previous Comments:
------------------------------------------------------------------------
[2002-08-03 01:00:11] php-bugs@lists.php.net
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2002-07-02 09:56:01] sniper@php.net
Please try this snapshot:
http://snaps.php.net/php4-latest.tar.gz
(has updated bundled libmysql)
------------------------------------------------------------------------
[2002-05-29 23:56:23] asautins@php.net
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.
------------------------------------------------------------------------
[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
------------------------------------------------------------------------
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