ID: 25211
User updated by: php at hottub dot ca
Reported By: php at hottub dot ca
-Status: Feedback
+Status: Open
Bug Type: Compile Failure
Operating System: AIX 5.1 ML4
PHP Version: 4.3.3
New Comment:
Haven't used GCC - previous versions were wildly
unstable on AIX, and only rarely produced usable
binaries. If someone can give me clear indication that
this has changed, I'd consider using it again.
Previous Comments:
------------------------------------------------------------------------
[2003-08-25 19:03:27] [EMAIL PROTECTED]
Does it work if you use GCC?
------------------------------------------------------------------------
[2003-08-25 12:56:58] php at hottub dot ca
Recompiled with the release version, and this issue has
not been corrected.
------------------------------------------------------------------------
[2003-08-23 09:54:54] php at hottub dot ca
When I added the remainder of the configure options,
the error occured again, despite the fact that the
definitions are the same in both places. Apparently
the AIX compiler throws 'unsigned' in front of 'char'
in header files.
When I edited both php_image.h and image.c to match
each other (simply 'char'), I got a successful compile.
Tests have been submitted to the QA site.
On a previous compile attempt, setting both definitions
to 'const char' resulted in the same error again. I
will attempt to determine if this is a compiler issue
for which there is a fix.
------------------------------------------------------------------------
[2003-08-22 22:46:13] php at hottub dot ca
Removing 'const' from line 60 of ext/standard/
php_image.c allowed a clean compile -- make test will
be submitted to list after additional configure flags
have been added.
------------------------------------------------------------------------
[2003-08-22 13:51:15] [EMAIL PROTECTED]
The declarations are exactly the same but maybe the compiler you use
doesn't understand const in return types. So please remove const from
the return type in both .c and .h file and tell me if that helps. If it
doesn't we need to find out why your compiler thinks the return type is
'unsigned char'.
------------------------------------------------------------------------
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/25211
--
Edit this bug report at http://bugs.php.net/?id=25211&edit=1
