ID: 20768
Comment by: kangus at acats dot com
Reported By: jphp at netjunky dot com
Status: Wont fix
Bug Type: Compile Failure
Operating System: Debian 3.0 Stable / Sparc
PHP Version: 4.3.0RC2
New Comment:
the tempnam issue stopped me dead on Yoper with php-4.3.2RC1/php-4.3.1
No amount of screwing around will get me past make.
Previous Comments:
------------------------------------------------------------------------
[2003-02-13 15:29:28] madmikey at unrealplayground dot com
I had this same problem on RH 7.2. I know it's supposed to be a
warning, but the build stops right there everytime I used the
--with-mysql configure option.
After looking hard for a fix, I finally changed line 103 of
my_tempnam.c to read:
res=mkstemp((char*) dir); /* Use stand. dir with prefix */
Now I'm not a C programmer by any stretch, but I was able to compile
successfully and install. Everything appears to be working correctly.
------------------------------------------------------------------------
[2002-12-13 11:59:40] [EMAIL PROTECTED]
does it stop the build or is it the last warning IN the build?
If it says "warning", there is no problem. Gcc 3.0x used to signal it
as an error and was quickly corrected. I hope you're not saying it's
status is back to "error" again, cause that would "not be very nice".
It's not a PHP problem either, when the gcc people decide to classify a
"MAY be used unsafe" statement, as an error.
------------------------------------------------------------------------
[2002-12-13 10:39:23] ben at thelocust dot org
it may be a warning, and not an error, but it sure brings my build to a
halt every time -- i'm not gcc genius, but how should we get around
this? I'm using gcc 3.2.1, libtool 1.4.3, btw.
------------------------------------------------------------------------
[2002-12-02 13:26:55] [EMAIL PROTECTED]
It's a warning, not an error.
------------------------------------------------------------------------
[2002-12-02 13:25:30] jphp at netjunky dot com
It may be safe, but it stops the compile. I can't build with the code
as is.
------------------------------------------------------------------------
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/20768
--
Edit this bug report at http://bugs.php.net/?id=20768&edit=1
