From noreply at sourceforge.net Thu Mar 3 15:04:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 3 15:05:01 2005 Subject: [Expat-bugs] [ expat-Bugs-1155849 ] missing expat_external.h in install Message-ID: Bugs item #1155849, was opened at 2005-03-03 06:04 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155849&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: missing expat_external.h in install Initial Comment: after configure make make install on expat 1.95.8 /usr/local/include/expat.h includes "expat_internal.h" I cannot found this header anywhere building on AIX 5.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155849&group_id=10127 From noreply at sourceforge.net Thu Mar 3 15:15:20 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 3 15:15:23 2005 Subject: [Expat-bugs] [ expat-Bugs-1155860 ] missing expat_external.h in install Message-ID: Bugs item #1155860, was opened at 2005-03-03 06:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155860&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: missing expat_external.h in install Initial Comment: after configure make make install on expat 1.95.8 /usr/local/include/expat.h includes "expat_internal.h" I cannot found this header anywhere building on AIX 5.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155860&group_id=10127 From noreply at sourceforge.net Thu Mar 3 15:57:32 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 3 15:57:35 2005 Subject: [Expat-bugs] [ expat-Bugs-1155890 ] missing expat_external.h in install Message-ID: Bugs item #1155890, was opened at 2005-03-03 06:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155890&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: missing expat_external.h in install Initial Comment: after configure make make install on expat 1.95.8 /usr/local/include/expat.h includes "expat_internal.h" I cannot found this header anywhere building on AIX 5.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155890&group_id=10127 From noreply at sourceforge.net Thu Mar 3 16:39:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 3 16:39:25 2005 Subject: [Expat-bugs] [ expat-Bugs-1155849 ] missing expat_external.h in install Message-ID: Bugs item #1155849, was opened at 2005-03-03 09:04 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155849&group_id=10127 Category: Build control Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: missing expat_external.h in install Initial Comment: after configure make make install on expat 1.95.8 /usr/local/include/expat.h includes "expat_internal.h" I cannot found this header anywhere building on AIX 5.1 ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-03 10:39 Message: Logged In: YES user_id=290026 Seems like a duplicate of bug #1000112. Fixed in CVS. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155849&group_id=10127 From noreply at sourceforge.net Thu Mar 3 16:39:53 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 3 16:39:56 2005 Subject: [Expat-bugs] [ expat-Bugs-1155860 ] missing expat_external.h in install Message-ID: Bugs item #1155860, was opened at 2005-03-03 09:15 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155860&group_id=10127 Category: Build control Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: missing expat_external.h in install Initial Comment: after configure make make install on expat 1.95.8 /usr/local/include/expat.h includes "expat_internal.h" I cannot found this header anywhere building on AIX 5.1 ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-03 10:39 Message: Logged In: YES user_id=290026 Seems like a duplicate of bug #1000112. Fixed in CVS. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155860&group_id=10127 From noreply at sourceforge.net Thu Mar 3 16:40:09 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 3 16:40:13 2005 Subject: [Expat-bugs] [ expat-Bugs-1155890 ] missing expat_external.h in install Message-ID: Bugs item #1155890, was opened at 2005-03-03 09:57 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155890&group_id=10127 Category: Build control Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: missing expat_external.h in install Initial Comment: after configure make make install on expat 1.95.8 /usr/local/include/expat.h includes "expat_internal.h" I cannot found this header anywhere building on AIX 5.1 ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-03 10:40 Message: Logged In: YES user_id=290026 Seems like a duplicate of bug #1000112. Fixed in CVS. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1155890&group_id=10127 From noreply at sourceforge.net Fri Mar 4 03:19:53 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 03:19:55 2005 Subject: [Expat-bugs] [ expat-Bugs-1156398 ] XML_UseForeignDTD forces incorrect WF checking Message-ID: Bugs item #1156398, was opened at 2005-03-03 21:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1156398&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Karl Waclawek (kwaclaw) Assigned to: Karl Waclawek (kwaclaw) Summary: XML_UseForeignDTD forces incorrect WF checking Initial Comment: When Expat calls the externalEntityRefHandler within the prolog, then it concludes that there must be an external subset, as there was an external identifier encountered. This information influences how the WFC: Entity Declared is checked. However, when Expat calls the externalEntityRefHandler in order to allow the application to supply an external subset when there was none, then Expat should not make this assumption unless an actual subset has been processed, as indicated by the dtd->paramEntityRead flag. The attached patch fixes this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1156398&group_id=10127 From noreply at sourceforge.net Fri Mar 4 04:11:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 04:11:25 2005 Subject: [Expat-bugs] [ expat-Patches-888879 ] gb2312 encoding handle Message-ID: Patches item #888879, was opened at 2004-02-01 22:15 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 Category: None Group: None Status: Open Resolution: Postponed Priority: 5 Submitted By: hunter,liu (szhunter) Assigned to: Nobody/Anonymous (nobody) Summary: gb2312 encoding handle Initial Comment: an patch for expat that can let expat handle gb2312 encoding xml file. Developer must use Xml_SetUnknowEncodingHandle() to call XML_GbEncodingHandle() ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-03 19:11 Message: Logged In: NO LQH ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-07 06:19 Message: Logged In: YES user_id=290026 Thank you for your patch! For now we will leave it as a standalone patch, as we have not yet determined in which way support for additional encodings should be added to Expat. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 From noreply at sourceforge.net Fri Mar 4 04:54:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 04:55:00 2005 Subject: [Expat-bugs] [ expat-Patches-888879 ] gb2312 encoding handle Message-ID: Patches item #888879, was opened at 2004-02-01 22:15 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 Category: None Group: None Status: Open Resolution: Postponed Priority: 5 Submitted By: hunter,liu (szhunter) Assigned to: Nobody/Anonymous (nobody) Summary: gb2312 encoding handle Initial Comment: an patch for expat that can let expat handle gb2312 encoding xml file. Developer must use Xml_SetUnknowEncodingHandle() to call XML_GbEncodingHandle() ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-03 19:54 Message: Logged In: NO LQH ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-03 19:11 Message: Logged In: NO LQH ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-07 06:19 Message: Logged In: YES user_id=290026 Thank you for your patch! For now we will leave it as a standalone patch, as we have not yet determined in which way support for additional encodings should be added to Expat. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 From noreply at sourceforge.net Fri Mar 4 05:18:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 05:18:12 2005 Subject: [Expat-bugs] [ expat-Bugs-1156398 ] XML_UseForeignDTD forces incorrect WF checking Message-ID: Bugs item #1156398, was opened at 2005-03-03 21:19 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1156398&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Karl Waclawek (kwaclaw) >Assigned to: Fred L. Drake, Jr. (fdrake) Summary: XML_UseForeignDTD forces incorrect WF checking Initial Comment: When Expat calls the externalEntityRefHandler within the prolog, then it concludes that there must be an external subset, as there was an external identifier encountered. This information influences how the WFC: Entity Declared is checked. However, when Expat calls the externalEntityRefHandler in order to allow the application to supply an external subset when there was none, then Expat should not make this assumption unless an actual subset has been processed, as indicated by the dtd->paramEntityRead flag. The attached patch fixes this. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-03 23:18 Message: Logged In: YES user_id=290026 We could use the following document for a test case:: ]> reference doesn't match delaration This document violates WFC: Entity Declared and Expat must return an error. However, if this document had an external subset then WFC: Entity Declared would not apply. Now, if one calls XML_UseForeignDTD() at the start of parsing the document above, then Expat 1.95.8 will accept the document, which is not correct. The patched version of Expat will return an error as it should. Assigned to Fred for testing. I really want this to be in release 2.0, as it improves the conformance against the XML_Test-Suite. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1156398&group_id=10127 From noreply at sourceforge.net Fri Mar 4 23:56:28 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 23:56:32 2005 Subject: [Expat-bugs] [ expat-Bugs-1157018 ] not well-formed ( invalid token) for Certain XML tags Message-ID: Bugs item #1157018, was opened at 2005-03-04 14:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 Category: XML::Parser (inactive) Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: not well-formed ( invalid token) for Certain XML tags Initial Comment: Hello : I have a well formed XML packet but xmlwf thows out error on certain tags adad.dadad test There are lot of other tags before and after these tags ( as shown above ). If i remove this particular section the xmlwf doesn;t show any error. The exact error is :10 : not well-formed (invalid token) 10 is actually the column position. and in the lines shown above , "=" is in the column position 10. Is there any newer version that handles these kind of tags ? or pl. suggest me a work around ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 From noreply at sourceforge.net Sat Mar 5 00:01:18 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 5 00:01:21 2005 Subject: [Expat-bugs] [ expat-Bugs-1157018 ] not well-formed ( invalid token) for Certain XML tags Message-ID: Bugs item #1157018, was opened at 2005-03-04 14:56 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 Category: XML::Parser (inactive) Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: not well-formed ( invalid token) for Certain XML tags Initial Comment: Hello : I have a well formed XML packet but xmlwf thows out error on certain tags adad.dadad test There are lot of other tags before and after these tags ( as shown above ). If i remove this particular section the xmlwf doesn;t show any error. The exact error is :10 : not well-formed (invalid token) 10 is actually the column position. and in the lines shown above , "=" is in the column position 10. Is there any newer version that handles these kind of tags ? or pl. suggest me a work around ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-04 15:01 Message: Logged In: NO Operating System is HP-UX. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 From noreply at sourceforge.net Sat Mar 5 00:02:40 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 5 00:02:43 2005 Subject: [Expat-bugs] [ expat-Bugs-1157018 ] not well-formed ( invalid token) for Certain XML tags Message-ID: Bugs item #1157018, was opened at 2005-03-04 14:56 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 Category: XML::Parser (inactive) Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: not well-formed ( invalid token) for Certain XML tags Initial Comment: Hello : I have a well formed XML packet but xmlwf thows out error on certain tags adad.dadad test There are lot of other tags before and after these tags ( as shown above ). If i remove this particular section the xmlwf doesn;t show any error. The exact error is :10 : not well-formed (invalid token) 10 is actually the column position. and in the lines shown above , "=" is in the column position 10. Is there any newer version that handles these kind of tags ? or pl. suggest me a work around ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-04 15:02 Message: Logged In: NO Operating System is HP-UX. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-04 15:01 Message: Logged In: NO Operating System is HP-UX. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 From noreply at sourceforge.net Sun Mar 13 06:26:28 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 13 06:26:31 2005 Subject: [Expat-bugs] [ expat-Bugs-1162302 ] Fault CharacterDataHandler if LF starts data Message-ID: Bugs item #1162302, was opened at 2005-03-12 21:26 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 Category: None Group: Not a Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fault CharacterDataHandler if LF starts data Initial Comment: When a tag's data start with LF (0x0A), I get XML_CharacterDataHandler with len=1 and s=0x0A instead of the actual data that comes after the LF. On the attached example I get the following calls to XML_CharacterDataHandler : - len =1, s=0x0A - len=6, s="closed" - len =1, s=0x0A - len =1, s=0x0A The last two calls for the function are problematic - I don't get the actual data that comes after the LF. The problem happens when the tag's data start with LF but has more characters after the LF. on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 From noreply at sourceforge.net Sun Mar 13 14:54:00 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 13 14:54:03 2005 Subject: [Expat-bugs] [ expat-Bugs-1162302 ] Fault CharacterDataHandler if LF starts data Message-ID: Bugs item #1162302, was opened at 2005-03-13 00:26 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 Category: None Group: Not a Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fault CharacterDataHandler if LF starts data Initial Comment: When a tag's data start with LF (0x0A), I get XML_CharacterDataHandler with len=1 and s=0x0A instead of the actual data that comes after the LF. On the attached example I get the following calls to XML_CharacterDataHandler : - len =1, s=0x0A - len=6, s="closed" - len =1, s=0x0A - len =1, s=0x0A The last two calls for the function are problematic - I don't get the actual data that comes after the LF. The problem happens when the tag's data start with LF but has more characters after the LF. on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-13 08:54 Message: Logged In: YES user_id=290026 Your attached example does not have any LF directly before or after the string "closed". Please clarify your problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 From noreply at sourceforge.net Sun Mar 13 14:56:03 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 13 14:56:05 2005 Subject: [Expat-bugs] [ expat-Bugs-1157018 ] not well-formed ( invalid token) for Certain XML tags Message-ID: Bugs item #1157018, was opened at 2005-03-04 17:56 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 Category: XML::Parser (inactive) Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: not well-formed ( invalid token) for Certain XML tags Initial Comment: Hello : I have a well formed XML packet but xmlwf thows out error on certain tags adad.dadad test There are lot of other tags before and after these tags ( as shown above ). If i remove this particular section the xmlwf doesn;t show any error. The exact error is :10 : not well-formed (invalid token) 10 is actually the column position. and in the lines shown above , "=" is in the column position 10. Is there any newer version that handles these kind of tags ? or pl. suggest me a work around ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-13 08:56 Message: Logged In: YES user_id=290026 Show us your code - you may have a problem there. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-04 18:02 Message: Logged In: NO Operating System is HP-UX. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-04 18:01 Message: Logged In: NO Operating System is HP-UX. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1157018&group_id=10127 From noreply at sourceforge.net Mon Mar 14 05:36:45 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 14 05:36:48 2005 Subject: [Expat-bugs] [ expat-Bugs-1162302 ] Fault CharacterDataHandler if LF starts data Message-ID: Bugs item #1162302, was opened at 2005-03-12 21:26 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 Category: None Group: Not a Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fault CharacterDataHandler if LF starts data Initial Comment: When a tag's data start with LF (0x0A), I get XML_CharacterDataHandler with len=1 and s=0x0A instead of the actual data that comes after the LF. On the attached example I get the following calls to XML_CharacterDataHandler : - len =1, s=0x0A - len=6, s="closed" - len =1, s=0x0A - len =1, s=0x0A The last two calls for the function are problematic - I don't get the actual data that comes after the LF. The problem happens when the tag's data start with LF but has more characters after the LF. on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-13 20:36 Message: Logged In: NO The attached example has LF (0x0A) in the following cases: - before the text "sip:pep@example.com" - before the text "Full state presence document" In these 2 cases I receive XML_CharacterDataHandler with len=1 and s=0x0A only. The function is not called for the data AFTER the LF (In the example to "Full state presence document"). Is there a way to overcome this problem? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-13 05:54 Message: Logged In: YES user_id=290026 Your attached example does not have any LF directly before or after the string "closed". Please clarify your problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 From noreply at sourceforge.net Mon Mar 14 14:20:05 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 14 14:20:08 2005 Subject: [Expat-bugs] [ expat-Bugs-1162302 ] Fault CharacterDataHandler if LF starts data Message-ID: Bugs item #1162302, was opened at 2005-03-13 06:26 Message generated for change (Comment added) made by mike-rosky You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 Category: None Group: Not a Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fault CharacterDataHandler if LF starts data Initial Comment: When a tag's data start with LF (0x0A), I get XML_CharacterDataHandler with len=1 and s=0x0A instead of the actual data that comes after the LF. On the attached example I get the following calls to XML_CharacterDataHandler : - len =1, s=0x0A - len=6, s="closed" - len =1, s=0x0A - len =1, s=0x0A The last two calls for the function are problematic - I don't get the actual data that comes after the LF. The problem happens when the tag's data start with LF but has more characters after the LF. on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- Comment By: Mike Rosky (mike-rosky) Date: 2005-03-14 14:20 Message: Logged In: YES user_id=1238831 I think that you (original sender) should examine your code, when and for which cases you're calling chardata handler. Please note that basically you have to (simplified) reset chardata buffer at the start element point and accumulate chardata value every time character data handler is invoked until parser calls the end element handler for that element. You can't suppose that chardata handler gets whole value in one call - actually in your case it's called twice because of CRLF, the first call returns CRLF (and eventually preceding chars), the second the rest of chardatas. Chardatas can even cross two source readings, which leads to same effect. You can try it when you add a character data handler to the outline.c example, where chardata handler just prints out the current part enclosed in brackets or something. Mike ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-14 05:36 Message: Logged In: NO The attached example has LF (0x0A) in the following cases: - before the text "sip:pep@example.com" - before the text "Full state presence document" In these 2 cases I receive XML_CharacterDataHandler with len=1 and s=0x0A only. The function is not called for the data AFTER the LF (In the example to "Full state presence document"). Is there a way to overcome this problem? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-13 14:54 Message: Logged In: YES user_id=290026 Your attached example does not have any LF directly before or after the string "closed". Please clarify your problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 From noreply at sourceforge.net Tue Mar 15 00:35:41 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 15 00:35:45 2005 Subject: [Expat-bugs] [ expat-Bugs-1162302 ] Fault CharacterDataHandler if LF starts data Message-ID: Bugs item #1162302, was opened at 2005-03-13 00:26 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 Category: None Group: Not a Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fault CharacterDataHandler if LF starts data Initial Comment: When a tag's data start with LF (0x0A), I get XML_CharacterDataHandler with len=1 and s=0x0A instead of the actual data that comes after the LF. On the attached example I get the following calls to XML_CharacterDataHandler : - len =1, s=0x0A - len=6, s="closed" - len =1, s=0x0A - len =1, s=0x0A The last two calls for the function are problematic - I don't get the actual data that comes after the LF. The problem happens when the tag's data start with LF but has more characters after the LF. on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-14 18:35 Message: Logged In: YES user_id=290026 Just to clarify - in Expat, a contiguous string of characters does not necessarily have to be reported through exactly one characterData() call-back. Often, line-breaks determine the boundary between call-backs. In the attached example, the character data for the element will likely be reported through three call-backs, as there are two line-breaks. ---------------------------------------------------------------------- Comment By: Mike Rosky (mike-rosky) Date: 2005-03-14 08:20 Message: Logged In: YES user_id=1238831 I think that you (original sender) should examine your code, when and for which cases you're calling chardata handler. Please note that basically you have to (simplified) reset chardata buffer at the start element point and accumulate chardata value every time character data handler is invoked until parser calls the end element handler for that element. You can't suppose that chardata handler gets whole value in one call - actually in your case it's called twice because of CRLF, the first call returns CRLF (and eventually preceding chars), the second the rest of chardatas. Chardatas can even cross two source readings, which leads to same effect. You can try it when you add a character data handler to the outline.c example, where chardata handler just prints out the current part enclosed in brackets or something. Mike ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-13 23:36 Message: Logged In: NO The attached example has LF (0x0A) in the following cases: - before the text "sip:pep@example.com" - before the text "Full state presence document" In these 2 cases I receive XML_CharacterDataHandler with len=1 and s=0x0A only. The function is not called for the data AFTER the LF (In the example to "Full state presence document"). Is there a way to overcome this problem? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-13 08:54 Message: Logged In: YES user_id=290026 Your attached example does not have any LF directly before or after the string "closed". Please clarify your problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1162302&group_id=10127 From noreply at sourceforge.net Sun Mar 27 13:52:20 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 27 13:52:24 2005 Subject: [Expat-bugs] [ expat-Bugs-1105135 ] Win64 portability warnings Message-ID: Bugs item #1105135, was opened at 2005-01-19 10:45 Message generated for change (Comment added) made by hgoldman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1105135&group_id=10127 Category: None Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Henrik Goldman (hgoldman) Assigned to: Nobody/Anonymous (nobody) Summary: Win64 portability warnings Initial Comment: I am trying to get my software ready for Win64 (AMD64 / IA64). Currently I'm using Visual Studio .NET 2003 with /Wp64 switch enabled. However theres some missing typecasts in expat to make it compile clean. Instead of waiting for someone to fix it I can probably do it myself but I'm only willing to if my changes will be considered for next release. I'm rather sure all the warnings will go away with apropriate typecasts. Please advise me how to continue. I'm using the downloaded version of expat 1.95.8: c:\myprog\shared\libs\expat-1.95.8\lib\xmltok_impl.c (1717) : warning C4244: 'return' : conversion from '__w64 int' to 'int', possible loss of data c:\myprog\shared\libs\expat-1.95.8\lib\xmltok_impl.c (1717) : warning C4244: 'return' : conversion from '__w64 int' to 'int', possible loss of data c:\myprog\shared\libs\expat-1.95.8\lib\xmltok_impl.c (1717) : warning C4244: 'return' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1604) : warning C4244: 'initializi ng' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1606) : warning C4244: 'initializi ng' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1615) : warning C4244: 'initializi ng' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1628) : warning C4244: 'initializi ng' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1642) : warning C4244: 'initializi ng' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1761) : warning C4244: 'return' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1770) : warning C4244: '=' : conve rsion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(1771) : warning C4244: '=' : conve rsion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(2318) : warning C4244: '=' : conve rsion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(2323) : warning C4244: '=' : conve rsion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(2511) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(2516) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(2541) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(2550) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(3067) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(3076) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(3938) : warning C4244: '=' : conve rsion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(4623) : warning C4244: '=' : conve rsion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(4669) : warning C4244: '=' : conve rsion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(5130) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(5135) : warning C4244: 'function' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(6017) : warning C4244: 'initializi ng' : conversion from '__w64 int' to 'int', possible loss of data ../../shared\libs\expat-1.95.8\lib\xmlparse.c(6031) : warning C4244: 'initializi ng' : conversion from '__w64 int' to 'int', possible loss of data ---------------------------------------------------------------------- >Comment By: Henrik Goldman (hgoldman) Date: 2005-03-27 13:52 Message: Logged In: YES user_id=798004 I don't understand why anyone hasn't looked at the patches yet? Sooner or later you will get more of these Win64 x64 requests because it's soon to be released as final and then people will want to write software for it. The patches I submitted are quite trivial which you will see when looking through them. Thanks. ---------------------------------------------------------------------- Comment By: Henrik Goldman (hgoldman) Date: 2005-02-07 16:11 Message: Logged In: YES user_id=798004 So did anyone look at the patch? ---------------------------------------------------------------------- Comment By: Henrik Goldman (hgoldman) Date: 2005-01-30 16:41 Message: Logged In: YES user_id=798004 Ok, so I patched my local 1.95.8 distribution and created a diff file. All the patches I made, are __int64 to int typecast warnings. All of them were fixed by adding parentheses and adding a (int) typecast. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2005-01-27 06:46 Message: Logged In: YES user_id=3066 We'll certainly consider patches. The best way to proceed would be to attach a patch to this bug report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1105135&group_id=10127 From noreply at sourceforge.net Mon Mar 28 01:15:13 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 01:15:17 2005 Subject: [Expat-bugs] [ expat-Bugs-577560 ] xmlparse.h missing Message-ID: Bugs item #577560, was opened at 2002-07-04 13:28 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=577560&group_id=10127 Category: None Group: None Status: Closed Resolution: Rejected Priority: 5 Submitted By: Joern P. Meier (ionflux) Assigned to: Nobody/Anonymous (nobody) Summary: xmlparse.h missing Initial Comment: Please include xmlparse/xmlparse.h in the distribution. It appears that Python 2.2.1 won't build the expat module if it cannot find the header. Python expat support is required to build libglade expat support, which is in turn needed to build gdm-2.4.0.0, which is required by GNOME 2. (I was able to workaround by downloading xmlparse.h from CVS) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-03-27 15:15 Message: Logged In: NO In file included from ../oapr/buildconfig.hpp:54, from app.cpp:48: ../oapr/oapr.hpp:53:21: prtypes.h: No such file or directory In file included from ../oapr/buildconfig.hpp:54, from app.cpp:48: ../oapr/oapr.hpp:62: error: `PRSize' does not name a type ../oapr/oapr.hpp:63: error: `PRInt32' does not name a type ../oapr/oapr.hpp:64: error: `PRInt16' does not name a type ../oapr/oapr.hpp:65: error: `PRInt32' does not name a type app.cpp:51:20: prinit.h: No such file or directory app.cpp: In member function `void oapr::app::initialize_noargs()': app.cpp:71: error: `PR_USER_THREAD' undeclared (first use this function) app.cpp:71: error: (Each undeclared identifier is reported only once for each function it appears in.) app.cpp:71: error: `PR_PRIORITY_NORMAL' undeclared (first use this function) app.cpp:71: error: `PR_Init' undeclared (first use this function) app.cpp:72: error: `PR_Initialized' undeclared (first use this function) app.cpp:72: error: `PR_FALSE' undeclared (first use this function) app.cpp: In destructor `oapr::app::~app()': app.cpp:95: error: `PR_Cleanup' undeclared (first use this function) app.cpp:95: error: `PR_FAILURE' undeclared (first use this function) make[3]: *** [app.lo] Ошибка 1 make[3]: Leaving directory `/opt/oapr-0.2/oapr' make[2]: *** [all-recursive] Ошибка 1 make[2]: Leaving directory `/opt/oapr-0.2/oapr' make[1]: *** [all-recursive] Ошибка 1 make[1]: Leaving directory `/opt/oapr-0.2' make: *** [all] Ошибка 2 ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2002-07-04 20:06 Message: Logged In: YES user_id=290026 xmlparse.h is not a part of Expat anymore. You should get the most recent version of Expat, i.e. the current version from CVS. Closed, since this is not a bug. Karl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=577560&group_id=10127 From noreply at sourceforge.net Mon Mar 28 06:01:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 06:01:14 2005 Subject: [Expat-bugs] [ expat-Bugs-1063934 ] building expat-1.95.8 for win32 with mingw Message-ID: Bugs item #1063934, was opened at 2004-11-10 16:35 Message generated for change (Comment added) made by heromyth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1063934&group_id=10127 Category: Build control Group: Third-party Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: building expat-1.95.8 for win32 with mingw Initial Comment: Hi! I'm compiling expat-1.95.8 for win32 with mingw in an cygwin-enviroment. During buildprocess i get following error: /bin/bash ./libtool --silent --mode=link g++-mingw -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -no-undefined -version-info 5:0:5 -rpath /wamas/test/erudig/WX/cygwin_win32/lib -Wl,--export-all,--kill-at -o libxmiexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo /usr/lib/gcc-lib/i686-pc-mingw32/3.3.3/../../../../i686-pc-mingw32/bin/ld: warning: cannot find entry symbol _DllMainCRTStartup@12; defaulting to 00401000 /usr/lib/gcc-lib/i686-pc-mingw32/3.3.3/../../../../i686-pc-mingw32/lib/libmingw32.a(main.o)(.text+0x106):main.c: undefined reference to `_WinMain@16' collect2: ld returned 1 exit status make: *** [libxmiexpat.la] Error 1 I suppose the libtool-script which is generated during configure is libtool-1.4.x. In this scipt they excluded some dll-entrypoints for cygwin and mingw. I replaced this script with the script of libtool-1.5.10 and all worked fine. So can you please replace the configure-scipt with an scipt which is generated with libtool-1.5 or higher. sincerely Elmar Rudigier ps: g++-mingw is is only a scipt which calls g++ whith the flag -mno-cygwin to exclude cygwin.dll during linking. ---------------------------------------------------------------------- Comment By: heromyth (heromyth) Date: 2005-03-28 04:01 Message: Logged In: YES user_id=1190746 Use the newer script to do Make, just get a static lib, there is no shared lib. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2005-01-27 04:53 Message: Logged In: YES user_id=3066 Using libtool 1.5.10 seems to work on my system (FC1), so I'll plan on using that for the next release. Assigning to me, since the version of libtool that gets used seems to be a matter of what's installed on the machine used to build the distribution. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-11-26 10:29 Message: Logged In: NO Please check http://sourceforge.net/tracker/index.php?func=detail&aid=1073661&group_id=10127&atid=110127 I think it is solved ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1063934&group_id=10127 From noreply at sourceforge.net Mon Mar 28 17:41:02 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 17:41:05 2005 Subject: [Expat-bugs] [ expat-Bugs-1171906 ] expat-2005-01-28 snapshot in Mingw's msys 1.0 Message-ID: Bugs item #1171906, was opened at 2005-03-28 15:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: heromyth (heromyth) Assigned to: Greg Stein (gstein) Summary: expat-2005-01-28 snapshot in Mingw's msys 1.0 Initial Comment: When I do Make, it is almost successful. At that time, I get the shared and statice libraries. During making, it show this: /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -O2 - Wall -Wmissing-pr ototypes -Wstrict-prototypes -fexceptions - DHAVE_EXPAT_CONFIG_H -o examples/ele ments examples/elements.o libexpat.la ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory gcc.exe: .libs/lt-examples/elements.c: No such file or directory gcc.exe: no input files SO I think there are some error in the file libtool. When I use another libtool of msys, it's OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127 From noreply at sourceforge.net Mon Mar 28 19:10:31 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 19:10:34 2005 Subject: [Expat-bugs] [ expat-Bugs-1171968 ] Solaris 9 build version 1.95.8 Message-ID: Bugs item #1171968, was opened at 2005-03-28 09:10 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Solaris 9 build version 1.95.8 Initial Comment: After running ./configure on Solaris 9 and executing make the following errors occur: "lib/xmlparse.c", line 855: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 919: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 925: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1179: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1184: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1424: parsing: macro recursion "lib/xmlparse.c", line 1427: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1430: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: parsing: macro recursion "lib/xmlparse.c", line 1436: finalBuffer: macro recursion "lib/xmlparse.c", line 1438: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1449: parsing: macro recursion "lib/xmlparse.c", line 1453: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1456: parsing: macro recursion "lib/xmlparse.c", line 1459: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1464: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1530: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1542: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1544: parsing: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1550: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1552: parsing: macro recursion "lib/xmlparse.c", line 1560: finalBuffer: macro recursion "lib/xmlparse.c", line 1567: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1570: parsing: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1577: parsing: macro recursion "lib/xmlparse.c", line 1592: parsing: macro recursion "lib/xmlparse.c", line 1671: parsing: macro recursion "lib/xmlparse.c", line 1675: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1677: parsing: macro recursion "lib/xmlparse.c", line 1681: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1687: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1690: parsing: macro recursion "lib/xmlparse.c", line 1693: parsing: macro recursion "lib/xmlparse.c", line 1695: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1701: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1703: parsing: macro recursion "lib/xmlparse.c", line 1705: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1707: parsing: macro recursion "lib/xmlparse.c", line 1714: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1717: parsing: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1723: finalBuffer: macro recursion "lib/xmlparse.c", line 1724: parsing: macro recursion "lib/xmlparse.c", line 2003: finalBuffer: macro recursion "lib/xmlparse.c", line 2039: finalBuffer: macro recursion "lib/xmlparse.c", line 2046: finalBuffer: macro recursion "lib/xmlparse.c", line 2053: finalBuffer: macro recursion "lib/xmlparse.c", line 2083: parsing: macro recursion "lib/xmlparse.c", line 2095: finalBuffer: macro recursion "lib/xmlparse.c", line 2101: finalBuffer: macro recursion "lib/xmlparse.c", line 2119: finalBuffer: macro recursion "lib/xmlparse.c", line 2569: parsing: macro recursion "lib/xmlparse.c", line 2988: finalBuffer: macro recursion "lib/xmlparse.c", line 3047: parsing: macro recursion "lib/xmlparse.c", line 3103: parsing: macro recursion "lib/xmlparse.c", line 3127: finalBuffer: macro recursion "lib/xmlparse.c", line 3172: parsing: macro recursion "lib/xmlparse.c", line 3412: finalBuffer: macro recursion "lib/xmlparse.c", line 3435: parsing: macro recursion "lib/xmlparse.c", line 3455: finalBuffer: macro recursion "lib/xmlparse.c", line 3475: finalBuffer: macro recursion "lib/xmlparse.c", line 3502: finalBuffer: macro recursion "lib/xmlparse.c", line 3519: finalBuffer: macro recursion "lib/xmlparse.c", line 3552: finalBuffer: macro recursion "lib/xmlparse.c", line 4499: parsing: macro recursion "lib/xmlparse.c", line 4530: parsing: macro recursion "lib/xmlparse.c", line 4554: finalBuffer: macro recursion "lib/xmlparse.c", line 4560: finalBuffer: macro recursion "lib/xmlparse.c", line 4569: parsing: macro recursion "lib/xmlparse.c", line 4622: parsing: macro recursion "lib/xmlparse.c", line 4668: parsing: macro recursion "lib/xmlparse.c", line 4686: finalBuffer: macro recursion "lib/xmlparse.c", line 4694: finalBuffer: macro recursion Updating xmlparse.c and expat.h from CVS results in fewer errors for the same type, as well as additional errors due to undefined variables/functions. email: dejan.nikolic@veritas.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 From noreply at sourceforge.net Mon Mar 28 19:25:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 19:25:45 2005 Subject: [Expat-bugs] [ expat-Bugs-1171968 ] Solaris 9 build version 1.95.8 Message-ID: Bugs item #1171968, was opened at 2005-03-28 12:10 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Solaris 9 build version 1.95.8 Initial Comment: After running ./configure on Solaris 9 and executing make the following errors occur: "lib/xmlparse.c", line 855: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 919: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 925: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1179: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1184: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1424: parsing: macro recursion "lib/xmlparse.c", line 1427: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1430: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: parsing: macro recursion "lib/xmlparse.c", line 1436: finalBuffer: macro recursion "lib/xmlparse.c", line 1438: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1449: parsing: macro recursion "lib/xmlparse.c", line 1453: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1456: parsing: macro recursion "lib/xmlparse.c", line 1459: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1464: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1530: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1542: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1544: parsing: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1550: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1552: parsing: macro recursion "lib/xmlparse.c", line 1560: finalBuffer: macro recursion "lib/xmlparse.c", line 1567: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1570: parsing: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1577: parsing: macro recursion "lib/xmlparse.c", line 1592: parsing: macro recursion "lib/xmlparse.c", line 1671: parsing: macro recursion "lib/xmlparse.c", line 1675: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1677: parsing: macro recursion "lib/xmlparse.c", line 1681: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1687: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1690: parsing: macro recursion "lib/xmlparse.c", line 1693: parsing: macro recursion "lib/xmlparse.c", line 1695: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1701: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1703: parsing: macro recursion "lib/xmlparse.c", line 1705: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1707: parsing: macro recursion "lib/xmlparse.c", line 1714: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1717: parsing: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1723: finalBuffer: macro recursion "lib/xmlparse.c", line 1724: parsing: macro recursion "lib/xmlparse.c", line 2003: finalBuffer: macro recursion "lib/xmlparse.c", line 2039: finalBuffer: macro recursion "lib/xmlparse.c", line 2046: finalBuffer: macro recursion "lib/xmlparse.c", line 2053: finalBuffer: macro recursion "lib/xmlparse.c", line 2083: parsing: macro recursion "lib/xmlparse.c", line 2095: finalBuffer: macro recursion "lib/xmlparse.c", line 2101: finalBuffer: macro recursion "lib/xmlparse.c", line 2119: finalBuffer: macro recursion "lib/xmlparse.c", line 2569: parsing: macro recursion "lib/xmlparse.c", line 2988: finalBuffer: macro recursion "lib/xmlparse.c", line 3047: parsing: macro recursion "lib/xmlparse.c", line 3103: parsing: macro recursion "lib/xmlparse.c", line 3127: finalBuffer: macro recursion "lib/xmlparse.c", line 3172: parsing: macro recursion "lib/xmlparse.c", line 3412: finalBuffer: macro recursion "lib/xmlparse.c", line 3435: parsing: macro recursion "lib/xmlparse.c", line 3455: finalBuffer: macro recursion "lib/xmlparse.c", line 3475: finalBuffer: macro recursion "lib/xmlparse.c", line 3502: finalBuffer: macro recursion "lib/xmlparse.c", line 3519: finalBuffer: macro recursion "lib/xmlparse.c", line 3552: finalBuffer: macro recursion "lib/xmlparse.c", line 4499: parsing: macro recursion "lib/xmlparse.c", line 4530: parsing: macro recursion "lib/xmlparse.c", line 4554: finalBuffer: macro recursion "lib/xmlparse.c", line 4560: finalBuffer: macro recursion "lib/xmlparse.c", line 4569: parsing: macro recursion "lib/xmlparse.c", line 4622: parsing: macro recursion "lib/xmlparse.c", line 4668: parsing: macro recursion "lib/xmlparse.c", line 4686: finalBuffer: macro recursion "lib/xmlparse.c", line 4694: finalBuffer: macro recursion Updating xmlparse.c and expat.h from CVS results in fewer errors for the same type, as well as additional errors due to undefined variables/functions. email: dejan.nikolic@veritas.com ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 12:25 Message: Logged In: YES user_id=290026 We had a similar problem in bug # 1021776. It was a compiler issue, however, we implemented a small workaround. Which compiler are you using? Btw, you should update *all* files from CVS, not just selected ones. Try again with everything at CVS revision. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 From noreply at sourceforge.net Mon Mar 28 20:44:15 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 20:44:19 2005 Subject: [Expat-bugs] [ expat-Bugs-1171968 ] Solaris 9 build version 1.95.8 Message-ID: Bugs item #1171968, was opened at 2005-03-28 11:10 Message generated for change (Comment added) made by dnikolic You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Solaris 9 build version 1.95.8 Initial Comment: After running ./configure on Solaris 9 and executing make the following errors occur: "lib/xmlparse.c", line 855: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 919: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 925: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1179: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1184: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1424: parsing: macro recursion "lib/xmlparse.c", line 1427: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1430: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: parsing: macro recursion "lib/xmlparse.c", line 1436: finalBuffer: macro recursion "lib/xmlparse.c", line 1438: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1449: parsing: macro recursion "lib/xmlparse.c", line 1453: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1456: parsing: macro recursion "lib/xmlparse.c", line 1459: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1464: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1530: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1542: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1544: parsing: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1550: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1552: parsing: macro recursion "lib/xmlparse.c", line 1560: finalBuffer: macro recursion "lib/xmlparse.c", line 1567: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1570: parsing: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1577: parsing: macro recursion "lib/xmlparse.c", line 1592: parsing: macro recursion "lib/xmlparse.c", line 1671: parsing: macro recursion "lib/xmlparse.c", line 1675: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1677: parsing: macro recursion "lib/xmlparse.c", line 1681: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1687: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1690: parsing: macro recursion "lib/xmlparse.c", line 1693: parsing: macro recursion "lib/xmlparse.c", line 1695: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1701: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1703: parsing: macro recursion "lib/xmlparse.c", line 1705: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1707: parsing: macro recursion "lib/xmlparse.c", line 1714: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1717: parsing: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1723: finalBuffer: macro recursion "lib/xmlparse.c", line 1724: parsing: macro recursion "lib/xmlparse.c", line 2003: finalBuffer: macro recursion "lib/xmlparse.c", line 2039: finalBuffer: macro recursion "lib/xmlparse.c", line 2046: finalBuffer: macro recursion "lib/xmlparse.c", line 2053: finalBuffer: macro recursion "lib/xmlparse.c", line 2083: parsing: macro recursion "lib/xmlparse.c", line 2095: finalBuffer: macro recursion "lib/xmlparse.c", line 2101: finalBuffer: macro recursion "lib/xmlparse.c", line 2119: finalBuffer: macro recursion "lib/xmlparse.c", line 2569: parsing: macro recursion "lib/xmlparse.c", line 2988: finalBuffer: macro recursion "lib/xmlparse.c", line 3047: parsing: macro recursion "lib/xmlparse.c", line 3103: parsing: macro recursion "lib/xmlparse.c", line 3127: finalBuffer: macro recursion "lib/xmlparse.c", line 3172: parsing: macro recursion "lib/xmlparse.c", line 3412: finalBuffer: macro recursion "lib/xmlparse.c", line 3435: parsing: macro recursion "lib/xmlparse.c", line 3455: finalBuffer: macro recursion "lib/xmlparse.c", line 3475: finalBuffer: macro recursion "lib/xmlparse.c", line 3502: finalBuffer: macro recursion "lib/xmlparse.c", line 3519: finalBuffer: macro recursion "lib/xmlparse.c", line 3552: finalBuffer: macro recursion "lib/xmlparse.c", line 4499: parsing: macro recursion "lib/xmlparse.c", line 4530: parsing: macro recursion "lib/xmlparse.c", line 4554: finalBuffer: macro recursion "lib/xmlparse.c", line 4560: finalBuffer: macro recursion "lib/xmlparse.c", line 4569: parsing: macro recursion "lib/xmlparse.c", line 4622: parsing: macro recursion "lib/xmlparse.c", line 4668: parsing: macro recursion "lib/xmlparse.c", line 4686: finalBuffer: macro recursion "lib/xmlparse.c", line 4694: finalBuffer: macro recursion Updating xmlparse.c and expat.h from CVS results in fewer errors for the same type, as well as additional errors due to undefined variables/functions. email: dejan.nikolic@veritas.com ---------------------------------------------------------------------- Comment By: Dejan Nikolic (dnikolic) Date: 2005-03-28 12:44 Message: Logged In: YES user_id=1248125 Kevin, pulled in a whole lib 1.76 revision and am still getting errors. Here they are: "lib/xmlparse.c", line 921: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 929: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1181: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1186: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1429: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1440: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1455: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1461: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1466: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1535: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1552: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1555: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1577: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1680: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1686: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1692: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1700: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1706: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1710: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1724: XML_STATUS_SUSPENDED: macro recursion Aparently if does not like redefinitions of macros. Compiler is cc version: Sun WorkShop 6 update 2 C 5.3 2001/05/15 Thanks. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 11:25 Message: Logged In: YES user_id=290026 We had a similar problem in bug # 1021776. It was a compiler issue, however, we implemented a small workaround. Which compiler are you using? Btw, you should update *all* files from CVS, not just selected ones. Try again with everything at CVS revision. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 From noreply at sourceforge.net Mon Mar 28 21:06:27 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 21:06:32 2005 Subject: [Expat-bugs] [ expat-Bugs-1171968 ] Solaris 9 build version 1.95.8 Message-ID: Bugs item #1171968, was opened at 2005-03-28 12:10 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Solaris 9 build version 1.95.8 Initial Comment: After running ./configure on Solaris 9 and executing make the following errors occur: "lib/xmlparse.c", line 855: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 919: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 925: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1179: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1184: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1424: parsing: macro recursion "lib/xmlparse.c", line 1427: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1430: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: parsing: macro recursion "lib/xmlparse.c", line 1436: finalBuffer: macro recursion "lib/xmlparse.c", line 1438: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1449: parsing: macro recursion "lib/xmlparse.c", line 1453: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1456: parsing: macro recursion "lib/xmlparse.c", line 1459: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1464: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1530: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1542: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1544: parsing: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1550: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1552: parsing: macro recursion "lib/xmlparse.c", line 1560: finalBuffer: macro recursion "lib/xmlparse.c", line 1567: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1570: parsing: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1577: parsing: macro recursion "lib/xmlparse.c", line 1592: parsing: macro recursion "lib/xmlparse.c", line 1671: parsing: macro recursion "lib/xmlparse.c", line 1675: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1677: parsing: macro recursion "lib/xmlparse.c", line 1681: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1687: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1690: parsing: macro recursion "lib/xmlparse.c", line 1693: parsing: macro recursion "lib/xmlparse.c", line 1695: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1701: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1703: parsing: macro recursion "lib/xmlparse.c", line 1705: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1707: parsing: macro recursion "lib/xmlparse.c", line 1714: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1717: parsing: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1723: finalBuffer: macro recursion "lib/xmlparse.c", line 1724: parsing: macro recursion "lib/xmlparse.c", line 2003: finalBuffer: macro recursion "lib/xmlparse.c", line 2039: finalBuffer: macro recursion "lib/xmlparse.c", line 2046: finalBuffer: macro recursion "lib/xmlparse.c", line 2053: finalBuffer: macro recursion "lib/xmlparse.c", line 2083: parsing: macro recursion "lib/xmlparse.c", line 2095: finalBuffer: macro recursion "lib/xmlparse.c", line 2101: finalBuffer: macro recursion "lib/xmlparse.c", line 2119: finalBuffer: macro recursion "lib/xmlparse.c", line 2569: parsing: macro recursion "lib/xmlparse.c", line 2988: finalBuffer: macro recursion "lib/xmlparse.c", line 3047: parsing: macro recursion "lib/xmlparse.c", line 3103: parsing: macro recursion "lib/xmlparse.c", line 3127: finalBuffer: macro recursion "lib/xmlparse.c", line 3172: parsing: macro recursion "lib/xmlparse.c", line 3412: finalBuffer: macro recursion "lib/xmlparse.c", line 3435: parsing: macro recursion "lib/xmlparse.c", line 3455: finalBuffer: macro recursion "lib/xmlparse.c", line 3475: finalBuffer: macro recursion "lib/xmlparse.c", line 3502: finalBuffer: macro recursion "lib/xmlparse.c", line 3519: finalBuffer: macro recursion "lib/xmlparse.c", line 3552: finalBuffer: macro recursion "lib/xmlparse.c", line 4499: parsing: macro recursion "lib/xmlparse.c", line 4530: parsing: macro recursion "lib/xmlparse.c", line 4554: finalBuffer: macro recursion "lib/xmlparse.c", line 4560: finalBuffer: macro recursion "lib/xmlparse.c", line 4569: parsing: macro recursion "lib/xmlparse.c", line 4622: parsing: macro recursion "lib/xmlparse.c", line 4668: parsing: macro recursion "lib/xmlparse.c", line 4686: finalBuffer: macro recursion "lib/xmlparse.c", line 4694: finalBuffer: macro recursion Updating xmlparse.c and expat.h from CVS results in fewer errors for the same type, as well as additional errors due to undefined variables/functions. email: dejan.nikolic@veritas.com ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 14:06 Message: Logged In: YES user_id=290026 Looks like a compiler issue. Can you upgrade your compiler, or switch to gcc? ---------------------------------------------------------------------- Comment By: Dejan Nikolic (dnikolic) Date: 2005-03-28 13:44 Message: Logged In: YES user_id=1248125 Kevin, pulled in a whole lib 1.76 revision and am still getting errors. Here they are: "lib/xmlparse.c", line 921: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 929: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1181: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1186: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1429: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1440: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1455: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1461: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1466: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1535: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1552: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1555: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1577: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1680: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1686: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1692: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1700: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1706: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1710: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1724: XML_STATUS_SUSPENDED: macro recursion Aparently if does not like redefinitions of macros. Compiler is cc version: Sun WorkShop 6 update 2 C 5.3 2001/05/15 Thanks. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 12:25 Message: Logged In: YES user_id=290026 We had a similar problem in bug # 1021776. It was a compiler issue, however, we implemented a small workaround. Which compiler are you using? Btw, you should update *all* files from CVS, not just selected ones. Try again with everything at CVS revision. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 From noreply at sourceforge.net Mon Mar 28 22:47:26 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 22:47:34 2005 Subject: [Expat-bugs] [ expat-Bugs-1171968 ] Solaris 9 build version 1.95.8 Message-ID: Bugs item #1171968, was opened at 2005-03-28 11:10 Message generated for change (Comment added) made by dnikolic You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Solaris 9 build version 1.95.8 Initial Comment: After running ./configure on Solaris 9 and executing make the following errors occur: "lib/xmlparse.c", line 855: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 919: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 925: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1179: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1184: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1424: parsing: macro recursion "lib/xmlparse.c", line 1427: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1430: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: parsing: macro recursion "lib/xmlparse.c", line 1436: finalBuffer: macro recursion "lib/xmlparse.c", line 1438: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1449: parsing: macro recursion "lib/xmlparse.c", line 1453: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1456: parsing: macro recursion "lib/xmlparse.c", line 1459: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1464: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1530: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1542: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1544: parsing: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1550: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1552: parsing: macro recursion "lib/xmlparse.c", line 1560: finalBuffer: macro recursion "lib/xmlparse.c", line 1567: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1570: parsing: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1577: parsing: macro recursion "lib/xmlparse.c", line 1592: parsing: macro recursion "lib/xmlparse.c", line 1671: parsing: macro recursion "lib/xmlparse.c", line 1675: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1677: parsing: macro recursion "lib/xmlparse.c", line 1681: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1687: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1690: parsing: macro recursion "lib/xmlparse.c", line 1693: parsing: macro recursion "lib/xmlparse.c", line 1695: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1701: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1703: parsing: macro recursion "lib/xmlparse.c", line 1705: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1707: parsing: macro recursion "lib/xmlparse.c", line 1714: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1717: parsing: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1723: finalBuffer: macro recursion "lib/xmlparse.c", line 1724: parsing: macro recursion "lib/xmlparse.c", line 2003: finalBuffer: macro recursion "lib/xmlparse.c", line 2039: finalBuffer: macro recursion "lib/xmlparse.c", line 2046: finalBuffer: macro recursion "lib/xmlparse.c", line 2053: finalBuffer: macro recursion "lib/xmlparse.c", line 2083: parsing: macro recursion "lib/xmlparse.c", line 2095: finalBuffer: macro recursion "lib/xmlparse.c", line 2101: finalBuffer: macro recursion "lib/xmlparse.c", line 2119: finalBuffer: macro recursion "lib/xmlparse.c", line 2569: parsing: macro recursion "lib/xmlparse.c", line 2988: finalBuffer: macro recursion "lib/xmlparse.c", line 3047: parsing: macro recursion "lib/xmlparse.c", line 3103: parsing: macro recursion "lib/xmlparse.c", line 3127: finalBuffer: macro recursion "lib/xmlparse.c", line 3172: parsing: macro recursion "lib/xmlparse.c", line 3412: finalBuffer: macro recursion "lib/xmlparse.c", line 3435: parsing: macro recursion "lib/xmlparse.c", line 3455: finalBuffer: macro recursion "lib/xmlparse.c", line 3475: finalBuffer: macro recursion "lib/xmlparse.c", line 3502: finalBuffer: macro recursion "lib/xmlparse.c", line 3519: finalBuffer: macro recursion "lib/xmlparse.c", line 3552: finalBuffer: macro recursion "lib/xmlparse.c", line 4499: parsing: macro recursion "lib/xmlparse.c", line 4530: parsing: macro recursion "lib/xmlparse.c", line 4554: finalBuffer: macro recursion "lib/xmlparse.c", line 4560: finalBuffer: macro recursion "lib/xmlparse.c", line 4569: parsing: macro recursion "lib/xmlparse.c", line 4622: parsing: macro recursion "lib/xmlparse.c", line 4668: parsing: macro recursion "lib/xmlparse.c", line 4686: finalBuffer: macro recursion "lib/xmlparse.c", line 4694: finalBuffer: macro recursion Updating xmlparse.c and expat.h from CVS results in fewer errors for the same type, as well as additional errors due to undefined variables/functions. email: dejan.nikolic@veritas.com ---------------------------------------------------------------------- Comment By: Dejan Nikolic (dnikolic) Date: 2005-03-28 14:47 Message: Logged In: YES user_id=1248125 Unfortunatelly compiler upgrade is not an option. Any other workarounds? Thanks. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 13:06 Message: Logged In: YES user_id=290026 Looks like a compiler issue. Can you upgrade your compiler, or switch to gcc? ---------------------------------------------------------------------- Comment By: Dejan Nikolic (dnikolic) Date: 2005-03-28 12:44 Message: Logged In: YES user_id=1248125 Kevin, pulled in a whole lib 1.76 revision and am still getting errors. Here they are: "lib/xmlparse.c", line 921: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 929: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1181: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1186: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1429: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1440: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1455: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1461: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1466: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1535: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1552: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1555: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1577: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1680: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1686: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1692: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1700: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1706: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1710: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1724: XML_STATUS_SUSPENDED: macro recursion Aparently if does not like redefinitions of macros. Compiler is cc version: Sun WorkShop 6 update 2 C 5.3 2001/05/15 Thanks. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 11:25 Message: Logged In: YES user_id=290026 We had a similar problem in bug # 1021776. It was a compiler issue, however, we implemented a small workaround. Which compiler are you using? Btw, you should update *all* files from CVS, not just selected ones. Try again with everything at CVS revision. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 From noreply at sourceforge.net Tue Mar 29 15:11:07 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 29 15:11:12 2005 Subject: [Expat-bugs] [ expat-Bugs-1171968 ] Solaris 9 build version 1.95.8 Message-ID: Bugs item #1171968, was opened at 2005-03-28 12:10 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Solaris 9 build version 1.95.8 Initial Comment: After running ./configure on Solaris 9 and executing make the following errors occur: "lib/xmlparse.c", line 855: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 918: parsing: macro recursion "lib/xmlparse.c", line 919: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 925: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1146: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1159: parsing: macro recursion "lib/xmlparse.c", line 1179: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1184: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1411: parsing: macro recursion "lib/xmlparse.c", line 1424: parsing: macro recursion "lib/xmlparse.c", line 1427: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1430: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: parsing: macro recursion "lib/xmlparse.c", line 1436: finalBuffer: macro recursion "lib/xmlparse.c", line 1438: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1449: parsing: macro recursion "lib/xmlparse.c", line 1453: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1456: parsing: macro recursion "lib/xmlparse.c", line 1459: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1464: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1530: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1542: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1544: parsing: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1550: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1552: parsing: macro recursion "lib/xmlparse.c", line 1560: finalBuffer: macro recursion "lib/xmlparse.c", line 1567: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1570: parsing: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1577: parsing: macro recursion "lib/xmlparse.c", line 1592: parsing: macro recursion "lib/xmlparse.c", line 1671: parsing: macro recursion "lib/xmlparse.c", line 1675: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1677: parsing: macro recursion "lib/xmlparse.c", line 1681: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1687: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1690: parsing: macro recursion "lib/xmlparse.c", line 1693: parsing: macro recursion "lib/xmlparse.c", line 1695: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1701: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1703: parsing: macro recursion "lib/xmlparse.c", line 1705: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1707: parsing: macro recursion "lib/xmlparse.c", line 1714: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1717: parsing: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1723: finalBuffer: macro recursion "lib/xmlparse.c", line 1724: parsing: macro recursion "lib/xmlparse.c", line 2003: finalBuffer: macro recursion "lib/xmlparse.c", line 2039: finalBuffer: macro recursion "lib/xmlparse.c", line 2046: finalBuffer: macro recursion "lib/xmlparse.c", line 2053: finalBuffer: macro recursion "lib/xmlparse.c", line 2083: parsing: macro recursion "lib/xmlparse.c", line 2095: finalBuffer: macro recursion "lib/xmlparse.c", line 2101: finalBuffer: macro recursion "lib/xmlparse.c", line 2119: finalBuffer: macro recursion "lib/xmlparse.c", line 2569: parsing: macro recursion "lib/xmlparse.c", line 2988: finalBuffer: macro recursion "lib/xmlparse.c", line 3047: parsing: macro recursion "lib/xmlparse.c", line 3103: parsing: macro recursion "lib/xmlparse.c", line 3127: finalBuffer: macro recursion "lib/xmlparse.c", line 3172: parsing: macro recursion "lib/xmlparse.c", line 3412: finalBuffer: macro recursion "lib/xmlparse.c", line 3435: parsing: macro recursion "lib/xmlparse.c", line 3455: finalBuffer: macro recursion "lib/xmlparse.c", line 3475: finalBuffer: macro recursion "lib/xmlparse.c", line 3502: finalBuffer: macro recursion "lib/xmlparse.c", line 3519: finalBuffer: macro recursion "lib/xmlparse.c", line 3552: finalBuffer: macro recursion "lib/xmlparse.c", line 4499: parsing: macro recursion "lib/xmlparse.c", line 4530: parsing: macro recursion "lib/xmlparse.c", line 4554: finalBuffer: macro recursion "lib/xmlparse.c", line 4560: finalBuffer: macro recursion "lib/xmlparse.c", line 4569: parsing: macro recursion "lib/xmlparse.c", line 4622: parsing: macro recursion "lib/xmlparse.c", line 4668: parsing: macro recursion "lib/xmlparse.c", line 4686: finalBuffer: macro recursion "lib/xmlparse.c", line 4694: finalBuffer: macro recursion Updating xmlparse.c and expat.h from CVS results in fewer errors for the same type, as well as additional errors due to undefined variables/functions. email: dejan.nikolic@veritas.com ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-29 08:11 Message: Logged In: YES user_id=290026 Either switch to gcc (it is free), or investigate if there are compiler options which increase standards adherence. In the latter case the configure script could be fixed, I guess. ---------------------------------------------------------------------- Comment By: Dejan Nikolic (dnikolic) Date: 2005-03-28 15:47 Message: Logged In: YES user_id=1248125 Unfortunatelly compiler upgrade is not an option. Any other workarounds? Thanks. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 14:06 Message: Logged In: YES user_id=290026 Looks like a compiler issue. Can you upgrade your compiler, or switch to gcc? ---------------------------------------------------------------------- Comment By: Dejan Nikolic (dnikolic) Date: 2005-03-28 13:44 Message: Logged In: YES user_id=1248125 Kevin, pulled in a whole lib 1.76 revision and am still getting errors. Here they are: "lib/xmlparse.c", line 921: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 927: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 929: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1181: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1186: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1429: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1432: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1440: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1455: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1461: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1466: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1535: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1547: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1552: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1555: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1572: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1577: XML_STATUS_SUSPENDED: macro recursion "lib/xmlparse.c", line 1680: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1686: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1692: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1700: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1706: XML_STATUS_OK: macro recursion "lib/xmlparse.c", line 1710: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1719: XML_STATUS_ERROR: macro recursion "lib/xmlparse.c", line 1724: XML_STATUS_SUSPENDED: macro recursion Aparently if does not like redefinitions of macros. Compiler is cc version: Sun WorkShop 6 update 2 C 5.3 2001/05/15 Thanks. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-28 12:25 Message: Logged In: YES user_id=290026 We had a similar problem in bug # 1021776. It was a compiler issue, however, we implemented a small workaround. Which compiler are you using? Btw, you should update *all* files from CVS, not just selected ones. Try again with everything at CVS revision. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171968&group_id=10127 From noreply at sourceforge.net Wed Mar 30 02:15:15 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 30 02:15:20 2005 Subject: [Expat-bugs] [ expat-Bugs-1171906 ] expat-2005-01-28 snapshot in Mingw's msys 1.0 Message-ID: Bugs item #1171906, was opened at 2005-03-28 15:41 Message generated for change (Comment added) made by heromyth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: heromyth (heromyth) Assigned to: Greg Stein (gstein) Summary: expat-2005-01-28 snapshot in Mingw's msys 1.0 Initial Comment: When I do Make, it is almost successful. At that time, I get the shared and statice libraries. During making, it show this: /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -O2 - Wall -Wmissing-pr ototypes -Wstrict-prototypes -fexceptions - DHAVE_EXPAT_CONFIG_H -o examples/ele ments examples/elements.o libexpat.la ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory gcc.exe: .libs/lt-examples/elements.c: No such file or directory gcc.exe: no input files SO I think there are some error in the file libtool. When I use another libtool of msys, it's OK. ---------------------------------------------------------------------- >Comment By: heromyth (heromyth) Date: 2005-03-30 00:15 Message: Logged In: YES user_id=1190746 There is a another question about the expat's libraries. In msys 1.0, I get libexpat.dll.a , libexpat.a and expat-0.dll. I link my applications like this: -Ld:/some/dir/ -lexpat It always use libexpat.dll.a but not libexpat.a. So I have test it. When I rename libexpat.dll.a to libexpat-0.dll.a, now the linker use libexpat.a. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127 From noreply at sourceforge.net Wed Mar 30 04:41:00 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 30 04:41:06 2005 Subject: [Expat-bugs] [ expat-Bugs-1171906 ] expat-2005-01-28 snapshot in Mingw's msys 1.0 Message-ID: Bugs item #1171906, was opened at 2005-03-28 10:41 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: heromyth (heromyth) >Assigned to: Gerrit P. Haase (siebenschlaefer) Summary: expat-2005-01-28 snapshot in Mingw's msys 1.0 Initial Comment: When I do Make, it is almost successful. At that time, I get the shared and statice libraries. During making, it show this: /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -O2 - Wall -Wmissing-pr ototypes -Wstrict-prototypes -fexceptions - DHAVE_EXPAT_CONFIG_H -o examples/ele ments examples/elements.o libexpat.la ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory gcc.exe: .libs/lt-examples/elements.c: No such file or directory gcc.exe: no input files SO I think there are some error in the file libtool. When I use another libtool of msys, it's OK. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-29 21:41 Message: Logged In: YES user_id=290026 Assigned to our Cygwin expert - maybe he can help. ---------------------------------------------------------------------- Comment By: heromyth (heromyth) Date: 2005-03-29 19:15 Message: Logged In: YES user_id=1190746 There is a another question about the expat's libraries. In msys 1.0, I get libexpat.dll.a , libexpat.a and expat-0.dll. I link my applications like this: -Ld:/some/dir/ -lexpat It always use libexpat.dll.a but not libexpat.a. So I have test it. When I rename libexpat.dll.a to libexpat-0.dll.a, now the linker use libexpat.a. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127 From noreply at sourceforge.net Wed Mar 30 11:46:23 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 30 11:46:26 2005 Subject: [Expat-bugs] [ expat-Bugs-1171906 ] expat-2005-01-28 snapshot in Mingw's msys 1.0 Message-ID: Bugs item #1171906, was opened at 2005-03-28 17:41 Message generated for change (Comment added) made by siebenschlaefer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127 Category: Build control Group: Platform Specific >Status: Pending Resolution: None Priority: 5 Submitted By: heromyth (heromyth) Assigned to: Gerrit P. Haase (siebenschlaefer) Summary: expat-2005-01-28 snapshot in Mingw's msys 1.0 Initial Comment: When I do Make, it is almost successful. At that time, I get the shared and statice libraries. During making, it show this: /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -O2 - Wall -Wmissing-pr ototypes -Wstrict-prototypes -fexceptions - DHAVE_EXPAT_CONFIG_H -o examples/ele ments examples/elements.o libexpat.la ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory ./libtool: .libs/lt-examples/elements.c: No such file or directory gcc.exe: .libs/lt-examples/elements.c: No such file or directory gcc.exe: no input files SO I think there are some error in the file libtool. When I use another libtool of msys, it's OK. ---------------------------------------------------------------------- >Comment By: Gerrit P. Haase (siebenschlaefer) Date: 2005-03-30 11:46 Message: Logged In: YES user_id=76037 Older libtool releases have many bugs, for the latest expat release an older buggy libtool was used, if you get better results with newer libtool releases, then upgrade libtool for your build. Future releases probably will use a newer libtool, so probably this bug will be resolved automatically when libtool at the build machine is upgraded. Ther other question: the libraries naming scheme is: Static archive: libexpat.a Import library: libexpat.dll.a Shared library: (cyg)expat-0.dll If you want to link against the static archive please use the -static ld switch with your link command, ld takes care about it and uses the static archive to build executables independant of the shared library. Hth, Gerrit ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2005-03-30 04:41 Message: Logged In: YES user_id=290026 Assigned to our Cygwin expert - maybe he can help. ---------------------------------------------------------------------- Comment By: heromyth (heromyth) Date: 2005-03-30 02:15 Message: Logged In: YES user_id=1190746 There is a another question about the expat's libraries. In msys 1.0, I get libexpat.dll.a , libexpat.a and expat-0.dll. I link my applications like this: -Ld:/some/dir/ -lexpat It always use libexpat.dll.a but not libexpat.a. So I have test it. When I rename libexpat.dll.a to libexpat-0.dll.a, now the linker use libexpat.a. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127