#41346 [Fbk->Csd]: segmentation fault on domxml_document_parser
ID: 41346 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl -Status: Feedback +Status: Closed Bug Type: *XML functions Operating System: Linux PHP Version: 4.4.7 New Comment: Haven't seen a segmentation fault since the upgrade of libxml2. Still strange it didn't occur with PHP 4.4.6 Previous Comments: [2007-05-11 11:52:02] wouter at widexs dot nl I've updated libxml2 (2.6.28), so I'll monitor for a while if the segmentation faults still occur. However, still weird that 4.4.6 did never give these segmentation faults, and 4.4.7 is compiled against the same libxml2 version (2.6.23, bit old perhaps) [2007-05-10 13:22:00] [EMAIL PROTECTED] Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with , is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. You might want to try a newer libxml2 version as it looks like the crash might be caused there. (cant be sure without a reproduceable case though) [2007-05-10 07:53:07] wouter at widexs dot nl Description: PHP 4.4.7 as Apache 2.0.59 DSO module gives a segmentation fault when parsing specific xml code. I've been unable to locate the exact code as of yet that triggers this. (since multiple clients use the piece of code i found in the backtrace) A 'bt full' is also available, which might reveal more info for you. I've disabled any Zend + 3rd-party extensions, thus only PHP-only extensions built-in. Reproduce code: --- Don't have it, though it has to be something like this : #16 0xb75b8952 in domxml_document_parser (mode=144905360, loadtype=0, source=0x8ac77e4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\";>\r\nhttp://www.w3.org/1999/xhtml\";>\r\nhttp://gmpg.org/x";..., data=0x0) at /opt/install/widexs_apache_2006_026/php-4.4.7/ext/domxml/php_domxml.c:4006 Which is used in WordPress CMS if I'm correct. Expected result: No segmentation fault :) Actual result: -- backtrace : (gdb) bt #0 0xb7a21df3 in free () from /lib/libc.so.6 #1 0xb6faf788 in xmlResetError__internal_alias (err=0xbfd65360) at error.c:871 #2 0xb6faeb94 in __xmlRaiseError (schannel=0, channel=0xb75b2ebc , data=0xbfd651e0, ctx=0xbfd651e0, nod=0x8ae0ee8, domain=23, code=504, level=XML_ERR_ERROR, file=0x0, line=-2147483636, str1=0x8b247f8 "ul", str2=0x8b247f8 "ul", str3=0xbfd62690 "()", int1=35, col=1, msg=0xb70706a0 "Element %s content does not follow the DTD, expecting %s, got %s\n") at error.c:534 #3 0xb6fda6f8 in xmlErrValidNode (ctxt=0x23, node=0x8ae0ee8, error=XML_DTD_CONTENT_MODEL, msg=0xb70706a0 "Element %s content does not follow the DTD, expecting %s, got %s\n", str1=0xb7adc4a4 "", str2=0xbfd63a20 "(li)+", str3=0xbfd62690 "()") at valid.c:152 #4 0xb6fe0763 in xmlValidateElementContent (ctxt=0x8a314fc, child=0x8ae0f38, elemDecl=0xbfd62690, warn=1, parent=0x8ae0ee8) at valid.c:5366 #5 0xb6fe15f6 in xmlValidateOneElement__internal_alias (ctxt=0x8a314fc, doc=0x8ae0f38, elem=0x8ae0ee8) at valid.c:6052 #6 0xb705b5d4 in xmlSAX2EndElementNs__internal_alias (ctx=0x8a31490, localname=0x8b06f4a "ul", prefix=0x0, URI=0x8b06ddf "http://www.w3.org/1999/xhtml";) at SAX2.c:2315 #7 0xb6fbf56e in xmlParseEndTag2 (ctxt=0x8a31490, prefix=0x0, URI=0x8b06ddf "http://www.w3.org/1999/xhtml";, line=28, nsNr=0, tlen=0) at parser.c:8207 #8 0xb6fbff9d in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8542 #9 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #10 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #11 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #12 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #13 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #14 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #15 0xb6fc1133 in xmlParseDocument__internal_alias (ctxt=0x8a31490) at parser.c:9129 #16 0xb75b8952 in domxml_document_parser (mode=144905360, loadtype=0, source=0x8ac77e4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\&q
#41346 [Fbk->Opn]: segmentation fault on domxml_document_parser
ID: 41346 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl -Status: Feedback +Status: Open Bug Type: *XML functions Operating System: Linux PHP Version: 4.4.7 New Comment: I've updated libxml2 (2.6.28), so I'll monitor for a while if the segmentation faults still occur. However, still weird that 4.4.6 did never give these segmentation faults, and 4.4.7 is compiled against the same libxml2 version (2.6.23, bit old perhaps) Previous Comments: [2007-05-10 13:22:00] [EMAIL PROTECTED] Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with , is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. You might want to try a newer libxml2 version as it looks like the crash might be caused there. (cant be sure without a reproduceable case though) [2007-05-10 07:53:07] wouter at widexs dot nl Description: PHP 4.4.7 as Apache 2.0.59 DSO module gives a segmentation fault when parsing specific xml code. I've been unable to locate the exact code as of yet that triggers this. (since multiple clients use the piece of code i found in the backtrace) A 'bt full' is also available, which might reveal more info for you. I've disabled any Zend + 3rd-party extensions, thus only PHP-only extensions built-in. Reproduce code: --- Don't have it, though it has to be something like this : #16 0xb75b8952 in domxml_document_parser (mode=144905360, loadtype=0, source=0x8ac77e4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\";>\r\nhttp://www.w3.org/1999/xhtml\";>\r\nhttp://gmpg.org/x";..., data=0x0) at /opt/install/widexs_apache_2006_026/php-4.4.7/ext/domxml/php_domxml.c:4006 Which is used in WordPress CMS if I'm correct. Expected result: No segmentation fault :) Actual result: -- backtrace : (gdb) bt #0 0xb7a21df3 in free () from /lib/libc.so.6 #1 0xb6faf788 in xmlResetError__internal_alias (err=0xbfd65360) at error.c:871 #2 0xb6faeb94 in __xmlRaiseError (schannel=0, channel=0xb75b2ebc , data=0xbfd651e0, ctx=0xbfd651e0, nod=0x8ae0ee8, domain=23, code=504, level=XML_ERR_ERROR, file=0x0, line=-2147483636, str1=0x8b247f8 "ul", str2=0x8b247f8 "ul", str3=0xbfd62690 "()", int1=35, col=1, msg=0xb70706a0 "Element %s content does not follow the DTD, expecting %s, got %s\n") at error.c:534 #3 0xb6fda6f8 in xmlErrValidNode (ctxt=0x23, node=0x8ae0ee8, error=XML_DTD_CONTENT_MODEL, msg=0xb70706a0 "Element %s content does not follow the DTD, expecting %s, got %s\n", str1=0xb7adc4a4 "", str2=0xbfd63a20 "(li)+", str3=0xbfd62690 "()") at valid.c:152 #4 0xb6fe0763 in xmlValidateElementContent (ctxt=0x8a314fc, child=0x8ae0f38, elemDecl=0xbfd62690, warn=1, parent=0x8ae0ee8) at valid.c:5366 #5 0xb6fe15f6 in xmlValidateOneElement__internal_alias (ctxt=0x8a314fc, doc=0x8ae0f38, elem=0x8ae0ee8) at valid.c:6052 #6 0xb705b5d4 in xmlSAX2EndElementNs__internal_alias (ctx=0x8a31490, localname=0x8b06f4a "ul", prefix=0x0, URI=0x8b06ddf "http://www.w3.org/1999/xhtml";) at SAX2.c:2315 #7 0xb6fbf56e in xmlParseEndTag2 (ctxt=0x8a31490, prefix=0x0, URI=0x8b06ddf "http://www.w3.org/1999/xhtml";, line=28, nsNr=0, tlen=0) at parser.c:8207 #8 0xb6fbff9d in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8542 #9 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #10 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #11 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #12 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #13 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #14 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #15 0xb6fc1133 in xmlParseDocument__internal_alias (ctxt=0x8a31490) at parser.c:9129 #16 0xb75b8952 in domxml_document_parser (mode=144905360, loadtype=0, source=0x8ac77e4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\";>\r\nhttp://www.w3.org/1999/xhtml\";>\r\nhttp://gmpg.org/x";..., data=0x0) at /opt/install/widexs_apache_2006_026/php-4.4.7/ext/domxml/php_domxml.c:4006 #17 0xb75b8a46 in zif_xmldoc (ht=2, return_value=0x8a31264, this_ptr=0
#41346 [NEW]: segmentation fault on domxml_document_parser
From: wouter at widexs dot nl Operating system: Linux PHP version: 4.4.7 PHP Bug Type: *XML functions Bug description: segmentation fault on domxml_document_parser Description: PHP 4.4.7 as Apache 2.0.59 DSO module gives a segmentation fault when parsing specific xml code. I've been unable to locate the exact code as of yet that triggers this. (since multiple clients use the piece of code i found in the backtrace) A 'bt full' is also available, which might reveal more info for you. I've disabled any Zend + 3rd-party extensions, thus only PHP-only extensions built-in. Reproduce code: --- Don't have it, though it has to be something like this : #16 0xb75b8952 in domxml_document_parser (mode=144905360, loadtype=0, source=0x8ac77e4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\";>\r\nhttp://www.w3.org/1999/xhtml\";>\r\nhttp://gmpg.org/x";..., data=0x0) at /opt/install/widexs_apache_2006_026/php-4.4.7/ext/domxml/php_domxml.c:4006 Which is used in WordPress CMS if I'm correct. Expected result: No segmentation fault :) Actual result: -- backtrace : (gdb) bt #0 0xb7a21df3 in free () from /lib/libc.so.6 #1 0xb6faf788 in xmlResetError__internal_alias (err=0xbfd65360) at error.c:871 #2 0xb6faeb94 in __xmlRaiseError (schannel=0, channel=0xb75b2ebc , data=0xbfd651e0, ctx=0xbfd651e0, nod=0x8ae0ee8, domain=23, code=504, level=XML_ERR_ERROR, file=0x0, line=-2147483636, str1=0x8b247f8 "ul", str2=0x8b247f8 "ul", str3=0xbfd62690 "()", int1=35, col=1, msg=0xb70706a0 "Element %s content does not follow the DTD, expecting %s, got %s\n") at error.c:534 #3 0xb6fda6f8 in xmlErrValidNode (ctxt=0x23, node=0x8ae0ee8, error=XML_DTD_CONTENT_MODEL, msg=0xb70706a0 "Element %s content does not follow the DTD, expecting %s, got %s\n", str1=0xb7adc4a4 "", str2=0xbfd63a20 "(li)+", str3=0xbfd62690 "()") at valid.c:152 #4 0xb6fe0763 in xmlValidateElementContent (ctxt=0x8a314fc, child=0x8ae0f38, elemDecl=0xbfd62690, warn=1, parent=0x8ae0ee8) at valid.c:5366 #5 0xb6fe15f6 in xmlValidateOneElement__internal_alias (ctxt=0x8a314fc, doc=0x8ae0f38, elem=0x8ae0ee8) at valid.c:6052 #6 0xb705b5d4 in xmlSAX2EndElementNs__internal_alias (ctx=0x8a31490, localname=0x8b06f4a "ul", prefix=0x0, URI=0x8b06ddf "http://www.w3.org/1999/xhtml";) at SAX2.c:2315 #7 0xb6fbf56e in xmlParseEndTag2 (ctxt=0x8a31490, prefix=0x0, URI=0x8b06ddf "http://www.w3.org/1999/xhtml";, line=28, nsNr=0, tlen=0) at parser.c:8207 #8 0xb6fbff9d in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8542 #9 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #10 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #11 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #12 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #13 0xb6fbfcef in xmlParseContent__internal_alias (ctxt=0x8a31490) at parser.c:8361 #14 0xb6fbff56 in xmlParseElement__internal_alias (ctxt=0x8a31490) at parser.c:8521 #15 0xb6fc1133 in xmlParseDocument__internal_alias (ctxt=0x8a31490) at parser.c:9129 #16 0xb75b8952 in domxml_document_parser (mode=144905360, loadtype=0, source=0x8ac77e4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\";>\r\nhttp://www.w3.org/1999/xhtml\";>\r\nhttp://gmpg.org/x";..., data=0x0) at /opt/install/widexs_apache_2006_026/php-4.4.7/ext/domxml/php_domxml.c:4006 #17 0xb75b8a46 in zif_xmldoc (ht=2, return_value=0x8a31264, this_ptr=0x0, return_value_used=1) at /opt/install/widexs_apache_2006_026/php-4.4.7/ext/domxml/php_domxml.c:4042 #18 0xb76d576a in execute (op_array=0x8a9ee10) at /opt/install/widexs_apache_2006_026/php-4.4.7/Zend/zend_execute.c:1681 #19 0xb76d551c in execute (op_array=0x8a40960) at /opt/install/widexs_apache_2006_026/php-4.4.7/Zend/zend_execute.c:1725 #20 0xb76d551c in execute (op_array=0x8984534) at /opt/install/widexs_apache_2006_026/php-4.4.7/Zend/zend_execute.c:1725 #21 0xb76c8fbf in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /opt/install/widexs_apache_2006_026/php-4.4.7/Zend/zend.c:939 #22 0xb76a4068 in php_execute_script (primary_file=0xbfd6ab70) at /opt/install/widexs_apache_2006_026/php-4.4.7/main/main.c:1757 #23 0xb76d96a7 in php_handler (r=0x8978608) at /opt/install/widexs_apache_2006_026/php-4.4.7/sapi/apache2handler/sapi_apache2.c:581 #24 0x080af902 in ap_run_handler () #25 0x080b0071 in ap_invoke_handler () #26 0x0809050d in ap_process_request () #27 0x0808a977 in ap_process_http_connection () #28 0x080bc422 in ap_run_process_connection () #29 0x080bc810 in ap_process_connection () #30 0x080ae19f in child_main () #31 0x080ae329 in make_child () #32 0x080ae39e in startup_children ()
#39401 [Opn]: conflicting types for utf8_mime2text
ID: 39401 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl Status: Open Bug Type: IMAP related Operating System: Linux PHP Version: 4.4.4 New Comment: That's not the point ;) It's the hope to have this fixed in 4.4.5 so we can use it without patching, just like in 5.x Previous Comments: [2007-01-26 12:33:40] dmda at yandex dot ru you can fix this with following: open ext/php_imap.c in your favorite editor, remove utf8_mime2text prototype (it's just wrong), find utf8_mime2text function call and add 3rd arguement: U8T_CANONICAL that's all tricks. [2007-01-22 15:53:01] php at aaronrubin dot com Are there any plans to patch this? The latest snapshots still have the same issue. [2007-01-03 19:42:41] jmoseley at pgtv dot com Can someone provide a patch for 4.4.4? The latest CVS release of 4.4.4 does not include the fix. I'd compile 5.2.0, but I am having linker problems since I run a Solaris box that uses a GCC compiler build with Sun's ld, blah, blah, blah. ---- [2006-11-17 10:26:53] wouter at widexs dot nl This was indeed fixed when using full-path, BUT it is still present in PHP 4.4.4 and PHP4-dev. (bugfix from 5.x not backported to 4.x) [2006-11-07 20:53:18] [EMAIL PROTECTED] It works just fine here as long as the fullpath to the library is specified ala /usr/local/imap-2006c 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/39401 -- Edit this bug report at http://bugs.php.net/?id=39401&edit=1
#39401 [Bgs->Opn]: conflicting types for utf8_mime2text
ID: 39401 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl -Status: Bogus +Status: Open Bug Type: IMAP related Operating System: Linux -PHP Version: 5.2.0 +PHP Version: 4.4.4 New Comment: This was indeed fixed when using full-path, BUT it is still present in PHP 4.4.4 and PHP4-dev. (bugfix from 5.x not backported to 4.x) Previous Comments: [2006-11-07 20:53:18] [EMAIL PROTECTED] It works just fine here as long as the fullpath to the library is specified ala /usr/local/imap-2006c [2006-11-07 19:58:52] wouter at widexs dot nl This patch fixes my problem ... --- php-5.2.0/configure Wed Nov 1 03:01:06 2006 +++ php-5.2.0-fix/configure Tue Nov 7 20:55:02 2006 @@ -45673,10 +45673,12 @@ rm -f conftest* +old_CPPFLAGS=$CPPFLAGS + CPPFLAGS=-I$IMAP_INC_DIR cat > conftest.$ac_ext < +#include "mail.h" EOF if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | egrep "mail_append_set" >/dev/null 2>&1; then @@ -45690,7 +45692,8 @@ fi rm -f conftest* - +CPPFLAGS=$old_CPPFLAGS + old_CPPFLAGS=$CPPFLAGS CPPFLAGS=-I$IMAP_INC_DIR cat > conftest.$ac_ext < to #include "$IMAP_INC_DIR/mail.h" It correctly works... -------------------- [2006-11-07 18:49:33] wouter at widexs dot nl It hasn't ... php-5.2.0/main/php_config.h:/* #undef HAVE_NEW_MIME2TEXT */ [2006-11-07 17:09:03] [EMAIL PROTECTED] Can you see if HAVE_NEW_MIME2TEXT is defined inside PHP's main.h ? 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/39401 -- Edit this bug report at http://bugs.php.net/?id=39401&edit=1
#39401 [Opn]: conflicting types for utf8_mime2text
ID: 39401 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl Status: Open Bug Type: IMAP related Operating System: Linux PHP Version: 5.2.0 New Comment: This patch fixes my problem ... --- php-5.2.0/configure Wed Nov 1 03:01:06 2006 +++ php-5.2.0-fix/configure Tue Nov 7 20:55:02 2006 @@ -45673,10 +45673,12 @@ rm -f conftest* +old_CPPFLAGS=$CPPFLAGS + CPPFLAGS=-I$IMAP_INC_DIR cat > conftest.$ac_ext < +#include "mail.h" EOF if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | egrep "mail_append_set" >/dev/null 2>&1; then @@ -45690,7 +45692,8 @@ fi rm -f conftest* - +CPPFLAGS=$old_CPPFLAGS + old_CPPFLAGS=$CPPFLAGS CPPFLAGS=-I$IMAP_INC_DIR cat > conftest.$ac_ext < to #include "$IMAP_INC_DIR/mail.h" It correctly works... -------------------- [2006-11-07 18:49:33] wouter at widexs dot nl It hasn't ... php-5.2.0/main/php_config.h:/* #undef HAVE_NEW_MIME2TEXT */ [2006-11-07 17:09:03] [EMAIL PROTECTED] Can you see if HAVE_NEW_MIME2TEXT is defined inside PHP's main.h ? ---------------- [2006-11-06 18:25:37] wouter at widexs dot nl Yes, it does :) grep "mail_append_set" src/c-client/mail.h SEARCHSET *mail_append_set (SEARCHSET *set,unsigned long msgno); [2006-11-06 17:01:26] [EMAIL PROTECTED] Does your imap's mail.h header contain the mail_append_set() function? 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/39401 -- Edit this bug report at http://bugs.php.net/?id=39401&edit=1
#39401 [Opn]: conflicting types for utf8_mime2text
ID: 39401 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl Status: Open Bug Type: IMAP related Operating System: Linux PHP Version: 5.2.0 New Comment: CHECKING FOR HAVE_NEW_MIME2TEXT configure:45679: ../imap-2006c1/c-client/mail.h: No such file or directory This file exists though... If I change configure from : #include <$IMAP_INC_DIR/mail.h> to #include "$IMAP_INC_DIR/mail.h" It correctly works... Previous Comments: [2006-11-07 18:49:33] wouter at widexs dot nl It hasn't ... php-5.2.0/main/php_config.h:/* #undef HAVE_NEW_MIME2TEXT */ [2006-11-07 17:09:03] [EMAIL PROTECTED] Can you see if HAVE_NEW_MIME2TEXT is defined inside PHP's main.h ? ---- [2006-11-06 18:25:37] wouter at widexs dot nl Yes, it does :) grep "mail_append_set" src/c-client/mail.h SEARCHSET *mail_append_set (SEARCHSET *set,unsigned long msgno); [2006-11-06 17:01:26] [EMAIL PROTECTED] Does your imap's mail.h header contain the mail_append_set() function? ------------ [2006-11-06 15:23:14] wouter at widexs dot nl Description: I get an error when trying to build PHP 5.2.0 with imap c-client 2006c1 (ftp://ftp.cac.washington.edu/mail/imap-2006c1.tar.Z) : /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' Which is correct, because: * PHP 5.2.0 : long utf8_mime2text(SIZEDTEXT *src, SIZEDTEXT *dst); * imap c-client 2006c1 : long utf8_mime2text (SIZEDTEXT *src,SIZEDTEXT *dst,long flags); Haven't tested with previous versions of PHP, but I assume the same will happen. IMAP c-client 2004g gives no problem. This could be seen as a DUP of #37948 and #38941, but it is still present in 5.2.0 ... Actual result: -- /bin/sh /opt/install/widexs_apache_2006_017/php-5.2.0/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/imap/ -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/ -DPHP_ATOM_INC -I/opt/install/widexs_apache_2006_017/php-5.2.0/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/main -I/opt/install/widexs_apache_2006_017/php-5.2.0 -I/usr/local/include/libxml2 -I/usr/local/ssl/include -I/usr/local/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/date/lib -I/usr/include/freetype2 -I/opt/install/widexs_apache_2006_017/imap-2006c1/c-client -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/oniguruma -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl/mbfl -I/usr/local/mysql/include/mysql -I/usr/local/pgsql/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/TSRM -I/opt/install/widexs_apache_2006_017/php-5.2.0/Zend-I/usr/include -g -O2 -c /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c -o ext/imap/php_imap.lo /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' -- Edit this bug report at http://bugs.php.net/?id=39401&edit=1
#39401 [Fbk->Opn]: conflicting types for utf8_mime2text
ID: 39401 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl -Status: Feedback +Status: Open Bug Type: IMAP related Operating System: Linux PHP Version: 5.2.0 New Comment: It hasn't ... php-5.2.0/main/php_config.h:/* #undef HAVE_NEW_MIME2TEXT */ Previous Comments: [2006-11-07 17:09:03] [EMAIL PROTECTED] Can you see if HAVE_NEW_MIME2TEXT is defined inside PHP's main.h ? [2006-11-06 18:25:37] wouter at widexs dot nl Yes, it does :) grep "mail_append_set" src/c-client/mail.h SEARCHSET *mail_append_set (SEARCHSET *set,unsigned long msgno); [2006-11-06 17:01:26] [EMAIL PROTECTED] Does your imap's mail.h header contain the mail_append_set() function? ---- [2006-11-06 15:23:14] wouter at widexs dot nl Description: I get an error when trying to build PHP 5.2.0 with imap c-client 2006c1 (ftp://ftp.cac.washington.edu/mail/imap-2006c1.tar.Z) : /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' Which is correct, because: * PHP 5.2.0 : long utf8_mime2text(SIZEDTEXT *src, SIZEDTEXT *dst); * imap c-client 2006c1 : long utf8_mime2text (SIZEDTEXT *src,SIZEDTEXT *dst,long flags); Haven't tested with previous versions of PHP, but I assume the same will happen. IMAP c-client 2004g gives no problem. This could be seen as a DUP of #37948 and #38941, but it is still present in 5.2.0 ... Actual result: -- /bin/sh /opt/install/widexs_apache_2006_017/php-5.2.0/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/imap/ -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/ -DPHP_ATOM_INC -I/opt/install/widexs_apache_2006_017/php-5.2.0/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/main -I/opt/install/widexs_apache_2006_017/php-5.2.0 -I/usr/local/include/libxml2 -I/usr/local/ssl/include -I/usr/local/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/date/lib -I/usr/include/freetype2 -I/opt/install/widexs_apache_2006_017/imap-2006c1/c-client -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/oniguruma -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl/mbfl -I/usr/local/mysql/include/mysql -I/usr/local/pgsql/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/TSRM -I/opt/install/widexs_apache_2006_017/php-5.2.0/Zend-I/usr/include -g -O2 -c /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c -o ext/imap/php_imap.lo /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' -- Edit this bug report at http://bugs.php.net/?id=39401&edit=1
#39401 [Fbk->Opn]: conflicting types for utf8_mime2text
ID: 39401 User updated by: wouter at widexs dot nl Reported By: wouter at widexs dot nl -Status: Feedback +Status: Open Bug Type: IMAP related Operating System: Linux PHP Version: 5.2.0 New Comment: Yes, it does :) grep "mail_append_set" src/c-client/mail.h SEARCHSET *mail_append_set (SEARCHSET *set,unsigned long msgno); Previous Comments: [2006-11-06 17:01:26] [EMAIL PROTECTED] Does your imap's mail.h header contain the mail_append_set() function? [2006-11-06 15:23:14] wouter at widexs dot nl Description: I get an error when trying to build PHP 5.2.0 with imap c-client 2006c1 (ftp://ftp.cac.washington.edu/mail/imap-2006c1.tar.Z) : /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' Which is correct, because: * PHP 5.2.0 : long utf8_mime2text(SIZEDTEXT *src, SIZEDTEXT *dst); * imap c-client 2006c1 : long utf8_mime2text (SIZEDTEXT *src,SIZEDTEXT *dst,long flags); Haven't tested with previous versions of PHP, but I assume the same will happen. IMAP c-client 2004g gives no problem. This could be seen as a DUP of #37948 and #38941, but it is still present in 5.2.0 ... Actual result: -- /bin/sh /opt/install/widexs_apache_2006_017/php-5.2.0/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/imap/ -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/ -DPHP_ATOM_INC -I/opt/install/widexs_apache_2006_017/php-5.2.0/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/main -I/opt/install/widexs_apache_2006_017/php-5.2.0 -I/usr/local/include/libxml2 -I/usr/local/ssl/include -I/usr/local/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/date/lib -I/usr/include/freetype2 -I/opt/install/widexs_apache_2006_017/imap-2006c1/c-client -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/oniguruma -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl/mbfl -I/usr/local/mysql/include/mysql -I/usr/local/pgsql/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/TSRM -I/opt/install/widexs_apache_2006_017/php-5.2.0/Zend-I/usr/include -g -O2 -c /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c -o ext/imap/php_imap.lo /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' -- Edit this bug report at http://bugs.php.net/?id=39401&edit=1
#39401 [NEW]: conflicting types for utf8_mime2text
From: wouter at widexs dot nl Operating system: Linux PHP version: 5.2.0 PHP Bug Type: IMAP related Bug description: conflicting types for utf8_mime2text Description: I get an error when trying to build PHP 5.2.0 with imap c-client 2006c1 (ftp://ftp.cac.washington.edu/mail/imap-2006c1.tar.Z) : /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' Which is correct, because: * PHP 5.2.0 : long utf8_mime2text(SIZEDTEXT *src, SIZEDTEXT *dst); * imap c-client 2006c1 : long utf8_mime2text (SIZEDTEXT *src,SIZEDTEXT *dst,long flags); Haven't tested with previous versions of PHP, but I assume the same will happen. IMAP c-client 2004g gives no problem. This could be seen as a DUP of #37948 and #38941, but it is still present in 5.2.0 ... Actual result: -- /bin/sh /opt/install/widexs_apache_2006_017/php-5.2.0/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/imap/ -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/ -DPHP_ATOM_INC -I/opt/install/widexs_apache_2006_017/php-5.2.0/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/main -I/opt/install/widexs_apache_2006_017/php-5.2.0 -I/usr/local/include/libxml2 -I/usr/local/ssl/include -I/usr/local/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/date/lib -I/usr/include/freetype2 -I/opt/install/widexs_apache_2006_017/imap-2006c1/c-client -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/oniguruma -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl -I/opt/install/widexs_apache_2006_017/php-5.2.0/ext/mbstring/libmbfl/mbfl -I/usr/local/mysql/include/mysql -I/usr/local/pgsql/include -I/opt/install/widexs_apache_2006_017/php-5.2.0/TSRM -I/opt/install/widexs_apache_2006_017/php-5.2.0/Zend-I/usr/include -g -O2 -c /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c -o ext/imap/php_imap.lo /opt/install/widexs_apache_2006_017/php-5.2.0/ext/imap/php_imap.c:79: conflicting types for `utf8_mime2text' /opt/install/widexs_apache_2006_017/imap-2006c1/c-client/utf8.h:548: previous declaration of `utf8_mime2text' -- Edit bug report at http://bugs.php.net/?id=39401&edit=1 -- Try a CVS snapshot (PHP 4.4): http://bugs.php.net/fix.php?id=39401&r=trysnapshot44 Try a CVS snapshot (PHP 5.2): http://bugs.php.net/fix.php?id=39401&r=trysnapshot52 Try a CVS snapshot (PHP 6.0): http://bugs.php.net/fix.php?id=39401&r=trysnapshot60 Fixed in CVS: http://bugs.php.net/fix.php?id=39401&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=39401&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=39401&r=needtrace Need Reproduce Script:http://bugs.php.net/fix.php?id=39401&r=needscript Try newer version:http://bugs.php.net/fix.php?id=39401&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=39401&r=support Expected behavior:http://bugs.php.net/fix.php?id=39401&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=39401&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=39401&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=39401&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=39401&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=39401&r=dst IIS Stability:http://bugs.php.net/fix.php?id=39401&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=39401&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=39401&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=39401&r=nozend MySQL Configuration Error:http://bugs.php.net/fix.php?id=39401&r=mysqlcfg
