|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #18643 libmysql/my_tempnam.c gives compiler warnings
Submitted: 2002-07-30 08:42 UTC Modified: 2002-11-22 04:12 UTC
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:0 (0.0%)
From: Assigned: georg (profile)
Status: Closed Package: Compile Warning
PHP Version: 4CVS-2002-08-14 OS: Compaq Tru64
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
21 - 19 = ?
Subscribe to this entry?

 [2002-07-30 08:42 UTC]
cc: Warning: /usr/users/nohn/php4-200207292100/ext/mysql/libmysql/my_tempnam.c, 
line 99: In this statement, the referenced type of the pointer value "(const cha
r ...)temp_env" is "pointer to const signed char", which is not compatible with 
"pointer to signed char". (ptrmismatch)
    environ=(const char**)temp_env;             /* May give warning */
cc: Warning: /usr/users/nohn/php4-200207292100/ext/mysql/libmysql/my_tempnam.c, 
line 105: In this statement, the referenced type of the pointer value "(const char ...)old_env" is "pointer to const signed char", which is not compatible with 
"pointer to signed char". (ptrmismatch)
  environ=(const char**)old_env;                /* May give warning */


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-08-13 22:27 UTC]
Sebastian is this still true with georg's recent work?
 [2002-08-14 18:02 UTC]
After chating with georg about this it seems that this bug has been fixed in the MySQL end of things, and we are just awaiting an update from thier end (Zak?).  
 [2002-08-23 11:58 UTC]
This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at
In case this was a documentation problem, the fix will show up soon at

In case this was a website problem, the change will show
up on the site and on the mirror sites in short time.
Thank you for the report, and for helping us make PHP better.

 [2002-11-22 01:55 UTC] info at chrisranjana dot com
I downloaded the latest snapshot i.e php4-STABLE-200211220430 today and compliled using the options  

./configure --with-mysql --with-gd=/usr/local --with-png-dir=/downloads/libpng-1.2.5 --with-zlib-dir=/downloads/zlib-1.1.4   --with-apxs=/usr/local/apache/bin/apxs --with-jpeg-dir=/downloads/jpeg-6b --with-mail --enable-track-vars

but still was getting the errors 

ext/mysql/libmysql/my_tempnam.lo: In function `my_tempnam':
/downloads/php4-STABLE-200211220430/ext/mysql/libmysql/my_tempnam.c:103: the use of `tempnam' is dangerous, better use `mkstemp'

then I went to  and downloaded their latest binary  mysql-3.23.53a-pc-linux-gnu-i686.tar.gz and installed it into /usr/local/mysql

and changed the configure options to 

./configure --with-mysql=/usr/local/mysql --with-gd=/usr/local --with-png-dir=/downloads/libpng-1.2.5 --with-zlib-dir=/downloads/zlib-1.1.4   --with-apxs=/usr/local/apache/bin/apxs --with-jpeg-dir=/downloads/jpeg-6b --with-mail --enable-track-vars

note:- --with-mysql=/usr/local/mysql

and it compiled perfect

 [2002-11-22 04:12 UTC]
the mysql client library that comes woth PHP uses mkstemp, thus the warning, on the other hand, it is implemented in a completely safe manner as they workaround the possible 'unsafetyness'. The latest mysql client lib (that you dl'd from seems to nuked it alltogether), hence no warning for you there. This is nothing to worry about, never was and won't be. at some point the bundled mysql client lib will be somehow updated and the warning will probably be gone then. Can we please keep that quiet from now on? :)

PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu May 23 12:01:32 2024 UTC