From noreply at sourceforge.net Thu Jul 3 04:32:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 3 06:32:41 2003 Subject: [Expat-bugs] [ expat-Bugs-765227 ] MacOSX build error with Expat 1.95.6 (included with PyXML) Message-ID: Bugs item #765227, was opened at 2003-07-03 12:32 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=765227&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: David Kaasen (davidkaasen) Assigned to: Greg Stein (gstein) Summary: MacOSX build error with Expat 1.95.6 (included with PyXML) Initial Comment: I had trouble with the expat 1.95.6 that is included with PyXML 0.8.2 on MacOSX 10.2.6. The build of PyXML gave error messages (but didn't halt) when compiling xmltok.c. It appears to be problems with the macros FASTCALL, PTRCALL and PTRFASTCALL in internal.h. Defining these to nothing made the compile succeed. Here is the diff output: *** PyXML-0.8.2/extensions/expat/lib/internal.h~ Sat Jan 25 12:18:09 2003 --- PyXML-0.8.2/extensions/expat/lib/internal.h Thu Jul 3 11:12:36 2003 *************** *** 27,33 **** --- 27,36 ---- and let's try this: */ + /* It doesn't work on MacOSX (__MACH__ and __APPLE__ == MacOSX). */ + #if !(defined(__MACH__) && defined(__APPLE__)) #define FASTCALL __attribute__((regparm(3))) #define PTRCALL #define PTRFASTCALL __attribute__((regparm(3))) + #endif /* Not MacOSX */ #elif defined(WIN32) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=765227&group_id=10127 From noreply at sourceforge.net Thu Jul 3 04:59:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 3 07:00:07 2003 Subject: [Expat-bugs] [ expat-Bugs-765227 ] MacOSX build error with Expat 1.95.6 (included with PyXML) Message-ID: Bugs item #765227, was opened at 2003-07-03 12:32 Message generated for change (Comment added) made by davidkaasen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=765227&group_id=10127 Category: Build control Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: David Kaasen (davidkaasen) Assigned to: Greg Stein (gstein) Summary: MacOSX build error with Expat 1.95.6 (included with PyXML) Initial Comment: I had trouble with the expat 1.95.6 that is included with PyXML 0.8.2 on MacOSX 10.2.6. The build of PyXML gave error messages (but didn't halt) when compiling xmltok.c. It appears to be problems with the macros FASTCALL, PTRCALL and PTRFASTCALL in internal.h. Defining these to nothing made the compile succeed. Here is the diff output: *** PyXML-0.8.2/extensions/expat/lib/internal.h~ Sat Jan 25 12:18:09 2003 --- PyXML-0.8.2/extensions/expat/lib/internal.h Thu Jul 3 11:12:36 2003 *************** *** 27,33 **** --- 27,36 ---- and let's try this: */ + /* It doesn't work on MacOSX (__MACH__ and __APPLE__ == MacOSX). */ + #if !(defined(__MACH__) && defined(__APPLE__)) #define FASTCALL __attribute__((regparm(3))) #define PTRCALL #define PTRFASTCALL __attribute__((regparm(3))) + #endif /* Not MacOSX */ #elif defined(WIN32) ---------------------------------------------------------------------- >Comment By: David Kaasen (davidkaasen) Date: 2003-07-03 12:59 Message: Logged In: YES user_id=20933 I should have mentioned that I am using Fink and Fink's Python distribution. Using /usr/bin/python instead only gives warnings, but then, there are problems with LDFLAGS containing "-arch i386" in /usr/lib/python2.2/config/Makefile. If that string is removed from LDFLAGS, everything seems to go well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=765227&group_id=10127 From noreply at sourceforge.net Tue Jul 8 03:15:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 05:18:41 2003 Subject: [Expat-bugs] [ expat-Bugs-767634 ] Build without XML_DTD define. Message-ID: Bugs item #767634, was opened at 2003-07-08 13: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=767634&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Maxim Petrovich Dementiev (maximdementiev) Assigned to: Greg Stein (gstein) Summary: Build without XML_DTD define. Initial Comment: Expat, Release 1.95.6 Platform: Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland Undefinded options: XML_NS and XML_DTD. Compile output: ------------------- begin ------------------------- Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland .\xmlparse.c: Error E2451 .\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding Error E2451 .\xmlparse.c 880: Undefined symbol 'externalParEntInitProcessor' in function XML_SetEncoding Error E2451 .\xmlparse.c 1102: Undefined symbol 'isParamEntity' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1102: Undefined symbol 'externalParEntInitProcessor' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1354: Undefined symbol 'isParamEntity' in function XML_SetParamEntityParsing Error E2451 .\xmlparse.c 1354: Undefined symbol 'externalParEntInitProcessor' in function XML_SetParamEntityParsing *** 6 errors in Compile *** -------------------- end ------------------------ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 From noreply at sourceforge.net Tue Jul 8 09:08:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 11:08:34 2003 Subject: [Expat-bugs] [ expat-Bugs-767634 ] Build without XML_DTD define. Message-ID: Bugs item #767634, was opened at 2003-07-08 05:15 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Maxim Petrovich Dementiev (maximdementiev) Assigned to: Greg Stein (gstein) Summary: Build without XML_DTD define. Initial Comment: Expat, Release 1.95.6 Platform: Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland Undefinded options: XML_NS and XML_DTD. Compile output: ------------------- begin ------------------------- Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland .\xmlparse.c: Error E2451 .\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding Error E2451 .\xmlparse.c 880: Undefined symbol 'externalParEntInitProcessor' in function XML_SetEncoding Error E2451 .\xmlparse.c 1102: Undefined symbol 'isParamEntity' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1102: Undefined symbol 'externalParEntInitProcessor' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1354: Undefined symbol 'isParamEntity' in function XML_SetParamEntityParsing Error E2451 .\xmlparse.c 1354: Undefined symbol 'externalParEntInitProcessor' in function XML_SetParamEntityParsing *** 6 errors in Compile *** -------------------- end ------------------------ ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 11:08 Message: Logged In: YES user_id=290026 When I am using the free command line compiler (bcc 5.5) then it works fine for me, both with XML_NS and XML_DTD undefined. I simply commented them out in winconfig.h. I was trying the version from CVS. Maybe you should give that one a try too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 From noreply at sourceforge.net Tue Jul 8 09:46:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 11:46:59 2003 Subject: [Expat-bugs] [ expat-Bugs-767634 ] Build without XML_DTD define. Message-ID: Bugs item #767634, was opened at 2003-07-08 13:15 Message generated for change (Comment added) made by maximdementiev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Maxim Petrovich Dementiev (maximdementiev) Assigned to: Greg Stein (gstein) Summary: Build without XML_DTD define. Initial Comment: Expat, Release 1.95.6 Platform: Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland Undefinded options: XML_NS and XML_DTD. Compile output: ------------------- begin ------------------------- Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland .\xmlparse.c: Error E2451 .\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding Error E2451 .\xmlparse.c 880: Undefined symbol 'externalParEntInitProcessor' in function XML_SetEncoding Error E2451 .\xmlparse.c 1102: Undefined symbol 'isParamEntity' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1102: Undefined symbol 'externalParEntInitProcessor' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1354: Undefined symbol 'isParamEntity' in function XML_SetParamEntityParsing Error E2451 .\xmlparse.c 1354: Undefined symbol 'externalParEntInitProcessor' in function XML_SetParamEntityParsing *** 6 errors in Compile *** -------------------- end ------------------------ ---------------------------------------------------------------------- >Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-08 19:46 Message: Logged In: YES user_id=501042 I'm sure it's error. Let's look at 'xmlparse.c'. Lines 610-626: ---------- begin ---------- #ifdef XML_DTD #define isParamEntity (parser->m_isParamEntity) #define useForeignDTD (parser->m_useForeignDTD) #define paramEntityParsing (parser->m_paramEntityParsing) #endif /* XML_DTD */ #define parsing \ (parentParser \ ? \ (isParamEntity \ ? \ (processor != externalParEntInitProcessor) \ : \ (processor != externalEntityInitProcessor)) \ : \ (processor != prologInitProcessor)) ---------- end ---------- We have symbol "isParamEntity" (only one declaration & definition - line 611) defined only if "XML_DTD" is definded. Right? I greped all files in "Expat-1.95.6" archive and found "isParamEntity" only in one file - 'xmlparse.c'. So macro "parsing" (line 616) always referes to symbol that may be undefined. And my compiler supports me in that issue saying: ---------- begin ---------- ..\lib\xmlparse.c: Error E2451 ..\lib\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding ---------- end ---------- because at line 880 we have call to macro "parsing". ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 19:08 Message: Logged In: YES user_id=290026 When I am using the free command line compiler (bcc 5.5) then it works fine for me, both with XML_NS and XML_DTD undefined. I simply commented them out in winconfig.h. I was trying the version from CVS. Maybe you should give that one a try too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 From noreply at sourceforge.net Tue Jul 8 10:58:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 12:59:11 2003 Subject: [Expat-bugs] [ expat-Bugs-767634 ] Build without XML_DTD define. Message-ID: Bugs item #767634, was opened at 2003-07-08 05:15 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Maxim Petrovich Dementiev (maximdementiev) Assigned to: Greg Stein (gstein) Summary: Build without XML_DTD define. Initial Comment: Expat, Release 1.95.6 Platform: Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland Undefinded options: XML_NS and XML_DTD. Compile output: ------------------- begin ------------------------- Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland .\xmlparse.c: Error E2451 .\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding Error E2451 .\xmlparse.c 880: Undefined symbol 'externalParEntInitProcessor' in function XML_SetEncoding Error E2451 .\xmlparse.c 1102: Undefined symbol 'isParamEntity' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1102: Undefined symbol 'externalParEntInitProcessor' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1354: Undefined symbol 'isParamEntity' in function XML_SetParamEntityParsing Error E2451 .\xmlparse.c 1354: Undefined symbol 'externalParEntInitProcessor' in function XML_SetParamEntityParsing *** 6 errors in Compile *** -------------------- end ------------------------ ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 12:58 Message: Logged In: YES user_id=290026 This is not the case in my version of xmlparse.c. I looked at fixed bugs and found bug #679754 which means it is fixed in CVS. As it currently looks we don't have this problem anymore. ---------------------------------------------------------------------- Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-08 11:46 Message: Logged In: YES user_id=501042 I'm sure it's error. Let's look at 'xmlparse.c'. Lines 610-626: ---------- begin ---------- #ifdef XML_DTD #define isParamEntity (parser->m_isParamEntity) #define useForeignDTD (parser->m_useForeignDTD) #define paramEntityParsing (parser->m_paramEntityParsing) #endif /* XML_DTD */ #define parsing \ (parentParser \ ? \ (isParamEntity \ ? \ (processor != externalParEntInitProcessor) \ : \ (processor != externalEntityInitProcessor)) \ : \ (processor != prologInitProcessor)) ---------- end ---------- We have symbol "isParamEntity" (only one declaration & definition - line 611) defined only if "XML_DTD" is definded. Right? I greped all files in "Expat-1.95.6" archive and found "isParamEntity" only in one file - 'xmlparse.c'. So macro "parsing" (line 616) always referes to symbol that may be undefined. And my compiler supports me in that issue saying: ---------- begin ---------- ..\lib\xmlparse.c: Error E2451 ..\lib\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding ---------- end ---------- because at line 880 we have call to macro "parsing". ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 11:08 Message: Logged In: YES user_id=290026 When I am using the free command line compiler (bcc 5.5) then it works fine for me, both with XML_NS and XML_DTD undefined. I simply commented them out in winconfig.h. I was trying the version from CVS. Maybe you should give that one a try too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 From noreply at sourceforge.net Tue Jul 8 14:13:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 16:13:34 2003 Subject: [Expat-bugs] [ expat-Bugs-768010 ] Extended characters not parsed correctly... Message-ID: Bugs item #768010, was opened at 2003-07-08 20:13 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=768010&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tony Palmer (etpalmer) Assigned to: Nobody/Anonymous (nobody) Summary: Extended characters not parsed correctly... Initial Comment: We have been using the expat parser for a couple years and have recently had need for parsing extended characters (128-255). Even though I specify "iso-8859- 1" in my parser create, it still is returning me incorrect character data. I am not sure what I am doing wrong. I am on a window 2000 platform with 1.95.6 now. I feed in the following: T?NY What I get out of the parse is (start,character data, hex of character data, end): MESSAGE T├?NY 54 ffffffc3 ffffff96 4e 59 MESSAGE My code is as follows: void startElement(void *userData, const char *name, const char **atts) { printf("%s\n",name); } void endElement(void *userData, const char *name) { printf("%s\n",name); } void characterData(void *userData, const XML_Char *s, int len) { char s2[256000]; int i; strncpy(s2,s,len); s2[len]=0; printf("%s\n", s2); for (i = 0; i < len; ++i) printf("%x ",s2[i]); printf("\n"); } void ParseXML(const char* csInput) { XML_Parser parser = XML_ParserCreate("iso- 8859-1"); int len = 0; XML_SetElementHandler(parser, startElement, endElement); XML_SetCharacterDataHandler(parser, characterData); len = strlen(csInput); printf("started XML parse\n"); if (!XML_Parse(parser, csInput, len, 1)) { printf("%s at line %d column %d\n", XML_ErrorString(XML_GetErrorCode (parser)), XML_GetCurrentLineNumber(parser), XML_GetCurrentColumnNumber (parser)); return; } XML_ParserFree(parser); } Any help would be appreciated. Thanks, Tony ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=768010&group_id=10127 From noreply at sourceforge.net Tue Jul 8 14:20:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 16:20:36 2003 Subject: [Expat-bugs] [ expat-Bugs-768010 ] Extended characters not parsed correctly... Message-ID: Bugs item #768010, was opened at 2003-07-08 16:13 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=768010&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tony Palmer (etpalmer) Assigned to: Nobody/Anonymous (nobody) Summary: Extended characters not parsed correctly... Initial Comment: We have been using the expat parser for a couple years and have recently had need for parsing extended characters (128-255). Even though I specify "iso-8859- 1" in my parser create, it still is returning me incorrect character data. I am not sure what I am doing wrong. I am on a window 2000 platform with 1.95.6 now. I feed in the following: T?NY What I get out of the parse is (start,character data, hex of character data, end): MESSAGE T├?NY 54 ffffffc3 ffffff96 4e 59 MESSAGE My code is as follows: void startElement(void *userData, const char *name, const char **atts) { printf("%s\n",name); } void endElement(void *userData, const char *name) { printf("%s\n",name); } void characterData(void *userData, const XML_Char *s, int len) { char s2[256000]; int i; strncpy(s2,s,len); s2[len]=0; printf("%s\n", s2); for (i = 0; i < len; ++i) printf("%x ",s2[i]); printf("\n"); } void ParseXML(const char* csInput) { XML_Parser parser = XML_ParserCreate("iso- 8859-1"); int len = 0; XML_SetElementHandler(parser, startElement, endElement); XML_SetCharacterDataHandler(parser, characterData); len = strlen(csInput); printf("started XML parse\n"); if (!XML_Parse(parser, csInput, len, 1)) { printf("%s at line %d column %d\n", XML_ErrorString(XML_GetErrorCode (parser)), XML_GetCurrentLineNumber(parser), XML_GetCurrentColumnNumber (parser)); return; } XML_ParserFree(parser); } Any help would be appreciated. Thanks, Tony ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 16:20 Message: Logged In: YES user_id=290026 Are you aware that Expat reports XML content encoded as UTF-8 or UTF-16 only? The document's encoding is irrelevant for that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=768010&group_id=10127 From noreply at sourceforge.net Wed Jul 9 01:07:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 9 03:07:37 2003 Subject: [Expat-bugs] [ expat-Bugs-767634 ] Build without XML_DTD define. Message-ID: Bugs item #767634, was opened at 2003-07-08 13:15 Message generated for change (Comment added) made by maximdementiev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Maxim Petrovich Dementiev (maximdementiev) Assigned to: Greg Stein (gstein) Summary: Build without XML_DTD define. Initial Comment: Expat, Release 1.95.6 Platform: Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland Undefinded options: XML_NS and XML_DTD. Compile output: ------------------- begin ------------------------- Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland .\xmlparse.c: Error E2451 .\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding Error E2451 .\xmlparse.c 880: Undefined symbol 'externalParEntInitProcessor' in function XML_SetEncoding Error E2451 .\xmlparse.c 1102: Undefined symbol 'isParamEntity' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1102: Undefined symbol 'externalParEntInitProcessor' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1354: Undefined symbol 'isParamEntity' in function XML_SetParamEntityParsing Error E2451 .\xmlparse.c 1354: Undefined symbol 'externalParEntInitProcessor' in function XML_SetParamEntityParsing *** 6 errors in Compile *** -------------------- end ------------------------ ---------------------------------------------------------------------- >Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-09 11:07 Message: Logged In: YES user_id=501042 Thank you for your job! I find library very good. PS: I downloaded 'expat_win32bin_1_95_6.exe' on 7 jule 2003 when bug is realy fixed already. Yes, CVS - is 'coolest' tool in the world - I respect. I think it will be nice if there will be file like bugs.txt (may be use section in existing one) where sum well-known bugs with status (fixed, open). PPS: Thank you again! ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 20:58 Message: Logged In: YES user_id=290026 This is not the case in my version of xmlparse.c. I looked at fixed bugs and found bug #679754 which means it is fixed in CVS. As it currently looks we don't have this problem anymore. ---------------------------------------------------------------------- Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-08 19:46 Message: Logged In: YES user_id=501042 I'm sure it's error. Let's look at 'xmlparse.c'. Lines 610-626: ---------- begin ---------- #ifdef XML_DTD #define isParamEntity (parser->m_isParamEntity) #define useForeignDTD (parser->m_useForeignDTD) #define paramEntityParsing (parser->m_paramEntityParsing) #endif /* XML_DTD */ #define parsing \ (parentParser \ ? \ (isParamEntity \ ? \ (processor != externalParEntInitProcessor) \ : \ (processor != externalEntityInitProcessor)) \ : \ (processor != prologInitProcessor)) ---------- end ---------- We have symbol "isParamEntity" (only one declaration & definition - line 611) defined only if "XML_DTD" is definded. Right? I greped all files in "Expat-1.95.6" archive and found "isParamEntity" only in one file - 'xmlparse.c'. So macro "parsing" (line 616) always referes to symbol that may be undefined. And my compiler supports me in that issue saying: ---------- begin ---------- ..\lib\xmlparse.c: Error E2451 ..\lib\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding ---------- end ---------- because at line 880 we have call to macro "parsing". ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 19:08 Message: Logged In: YES user_id=290026 When I am using the free command line compiler (bcc 5.5) then it works fine for me, both with XML_NS and XML_DTD undefined. I simply commented them out in winconfig.h. I was trying the version from CVS. Maybe you should give that one a try too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 From noreply at sourceforge.net Wed Jul 9 07:16:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 9 09:16:56 2003 Subject: [Expat-bugs] [ expat-Bugs-767634 ] Build without XML_DTD define. Message-ID: Bugs item #767634, was opened at 2003-07-08 05:15 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 Category: Build control Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Maxim Petrovich Dementiev (maximdementiev) Assigned to: Greg Stein (gstein) Summary: Build without XML_DTD define. Initial Comment: Expat, Release 1.95.6 Platform: Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland Undefinded options: XML_NS and XML_DTD. Compile output: ------------------- begin ------------------------- Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland .\xmlparse.c: Error E2451 .\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding Error E2451 .\xmlparse.c 880: Undefined symbol 'externalParEntInitProcessor' in function XML_SetEncoding Error E2451 .\xmlparse.c 1102: Undefined symbol 'isParamEntity' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1102: Undefined symbol 'externalParEntInitProcessor' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1354: Undefined symbol 'isParamEntity' in function XML_SetParamEntityParsing Error E2451 .\xmlparse.c 1354: Undefined symbol 'externalParEntInitProcessor' in function XML_SetParamEntityParsing *** 6 errors in Compile *** -------------------- end ------------------------ ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-09 09:16 Message: Logged In: YES user_id=290026 We haven't found time to build a new release from CVS yet. There is also one patch left to be reviewed. About the bug list: What is really missing is a display option for the bug tracker that shows the resolution type for closed bugs. I am closing this bug report now as a duplicate of bug #679754. ---------------------------------------------------------------------- Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-09 03:07 Message: Logged In: YES user_id=501042 Thank you for your job! I find library very good. PS: I downloaded 'expat_win32bin_1_95_6.exe' on 7 jule 2003 when bug is realy fixed already. Yes, CVS - is 'coolest' tool in the world - I respect. I think it will be nice if there will be file like bugs.txt (may be use section in existing one) where sum well-known bugs with status (fixed, open). PPS: Thank you again! ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 12:58 Message: Logged In: YES user_id=290026 This is not the case in my version of xmlparse.c. I looked at fixed bugs and found bug #679754 which means it is fixed in CVS. As it currently looks we don't have this problem anymore. ---------------------------------------------------------------------- Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-08 11:46 Message: Logged In: YES user_id=501042 I'm sure it's error. Let's look at 'xmlparse.c'. Lines 610-626: ---------- begin ---------- #ifdef XML_DTD #define isParamEntity (parser->m_isParamEntity) #define useForeignDTD (parser->m_useForeignDTD) #define paramEntityParsing (parser->m_paramEntityParsing) #endif /* XML_DTD */ #define parsing \ (parentParser \ ? \ (isParamEntity \ ? \ (processor != externalParEntInitProcessor) \ : \ (processor != externalEntityInitProcessor)) \ : \ (processor != prologInitProcessor)) ---------- end ---------- We have symbol "isParamEntity" (only one declaration & definition - line 611) defined only if "XML_DTD" is definded. Right? I greped all files in "Expat-1.95.6" archive and found "isParamEntity" only in one file - 'xmlparse.c'. So macro "parsing" (line 616) always referes to symbol that may be undefined. And my compiler supports me in that issue saying: ---------- begin ---------- ..\lib\xmlparse.c: Error E2451 ..\lib\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding ---------- end ---------- because at line 880 we have call to macro "parsing". ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 11:08 Message: Logged In: YES user_id=290026 When I am using the free command line compiler (bcc 5.5) then it works fine for me, both with XML_NS and XML_DTD undefined. I simply commented them out in winconfig.h. I was trying the version from CVS. Maybe you should give that one a try too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 From noreply at sourceforge.net Wed Jul 9 07:17:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 9 09:17:12 2003 Subject: [Expat-bugs] [ expat-Bugs-767634 ] Build without XML_DTD define. Message-ID: Bugs item #767634, was opened at 2003-07-08 05:15 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 Category: Build control Group: None Status: Closed Resolution: Duplicate Priority: 5 Submitted By: Maxim Petrovich Dementiev (maximdementiev) Assigned to: Greg Stein (gstein) Summary: Build without XML_DTD define. Initial Comment: Expat, Release 1.95.6 Platform: Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland Undefinded options: XML_NS and XML_DTD. Compile output: ------------------- begin ------------------------- Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland .\xmlparse.c: Error E2451 .\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding Error E2451 .\xmlparse.c 880: Undefined symbol 'externalParEntInitProcessor' in function XML_SetEncoding Error E2451 .\xmlparse.c 1102: Undefined symbol 'isParamEntity' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1102: Undefined symbol 'externalParEntInitProcessor' in function XML_SetReturnNSTriplet Error E2451 .\xmlparse.c 1354: Undefined symbol 'isParamEntity' in function XML_SetParamEntityParsing Error E2451 .\xmlparse.c 1354: Undefined symbol 'externalParEntInitProcessor' in function XML_SetParamEntityParsing *** 6 errors in Compile *** -------------------- end ------------------------ ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-09 09:17 Message: Logged In: YES user_id=290026 We haven't found time to build a new release from CVS yet. There is also one patch left to be reviewed. About the bug list: What is really missing is a display option for the bug tracker that shows the resolution type for closed bugs. I am closing this bug report now as a duplicate of bug #679754. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-09 09:16 Message: Logged In: YES user_id=290026 We haven't found time to build a new release from CVS yet. There is also one patch left to be reviewed. About the bug list: What is really missing is a display option for the bug tracker that shows the resolution type for closed bugs. I am closing this bug report now as a duplicate of bug #679754. ---------------------------------------------------------------------- Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-09 03:07 Message: Logged In: YES user_id=501042 Thank you for your job! I find library very good. PS: I downloaded 'expat_win32bin_1_95_6.exe' on 7 jule 2003 when bug is realy fixed already. Yes, CVS - is 'coolest' tool in the world - I respect. I think it will be nice if there will be file like bugs.txt (may be use section in existing one) where sum well-known bugs with status (fixed, open). PPS: Thank you again! ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 12:58 Message: Logged In: YES user_id=290026 This is not the case in my version of xmlparse.c. I looked at fixed bugs and found bug #679754 which means it is fixed in CVS. As it currently looks we don't have this problem anymore. ---------------------------------------------------------------------- Comment By: Maxim Petrovich Dementiev (maximdementiev) Date: 2003-07-08 11:46 Message: Logged In: YES user_id=501042 I'm sure it's error. Let's look at 'xmlparse.c'. Lines 610-626: ---------- begin ---------- #ifdef XML_DTD #define isParamEntity (parser->m_isParamEntity) #define useForeignDTD (parser->m_useForeignDTD) #define paramEntityParsing (parser->m_paramEntityParsing) #endif /* XML_DTD */ #define parsing \ (parentParser \ ? \ (isParamEntity \ ? \ (processor != externalParEntInitProcessor) \ : \ (processor != externalEntityInitProcessor)) \ : \ (processor != prologInitProcessor)) ---------- end ---------- We have symbol "isParamEntity" (only one declaration & definition - line 611) defined only if "XML_DTD" is definded. Right? I greped all files in "Expat-1.95.6" archive and found "isParamEntity" only in one file - 'xmlparse.c'. So macro "parsing" (line 616) always referes to symbol that may be undefined. And my compiler supports me in that issue saying: ---------- begin ---------- ..\lib\xmlparse.c: Error E2451 ..\lib\xmlparse.c 880: Undefined symbol 'isParamEntity' in function XML_SetEncoding ---------- end ---------- because at line 880 we have call to macro "parsing". ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 11:08 Message: Logged In: YES user_id=290026 When I am using the free command line compiler (bcc 5.5) then it works fine for me, both with XML_NS and XML_DTD undefined. I simply commented them out in winconfig.h. I was trying the version from CVS. Maybe you should give that one a try too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=767634&group_id=10127 From noreply at sourceforge.net Wed Jul 9 07:19:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 9 09:19:53 2003 Subject: [Expat-bugs] [ expat-Bugs-754228 ] Error running in multiprocesor machines Message-ID: Bugs item #754228, was opened at 2003-06-13 16:56 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=754228&group_id=10127 Category: None Group: Test Required >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Error running in multiprocesor machines Initial Comment: I have errors running in multiprocessor machines (and intenssive usage) that dissaperars when the parse operation is serialized. The errors even occurs if i do nothing in the handlers (only returning the control in each handler to the parser) Version 1.2 ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-09 09:19 Message: Logged In: YES user_id=290026 Closing this report - due to lack of follow-up by original user who submitted it. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-06-13 17:12 Message: Logged In: YES user_id=290026 Try with a later version. If that works, then use this version, as we do not branch older versions for bug fixes - or in other words: the fix for an older version is the newer one. Consequently, if this bug cannot be confirmed for the current version, then this report will be closed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=754228&group_id=10127 From noreply at sourceforge.net Wed Jul 9 09:19:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 9 11:20:01 2003 Subject: [Expat-bugs] [ expat-Bugs-768010 ] Extended characters not parsed correctly... Message-ID: Bugs item #768010, was opened at 2003-07-08 20:13 Message generated for change (Comment added) made by etpalmer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=768010&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tony Palmer (etpalmer) Assigned to: Nobody/Anonymous (nobody) Summary: Extended characters not parsed correctly... Initial Comment: We have been using the expat parser for a couple years and have recently had need for parsing extended characters (128-255). Even though I specify "iso-8859- 1" in my parser create, it still is returning me incorrect character data. I am not sure what I am doing wrong. I am on a window 2000 platform with 1.95.6 now. I feed in the following: T?NY What I get out of the parse is (start,character data, hex of character data, end): MESSAGE T├?NY 54 ffffffc3 ffffff96 4e 59 MESSAGE My code is as follows: void startElement(void *userData, const char *name, const char **atts) { printf("%s\n",name); } void endElement(void *userData, const char *name) { printf("%s\n",name); } void characterData(void *userData, const XML_Char *s, int len) { char s2[256000]; int i; strncpy(s2,s,len); s2[len]=0; printf("%s\n", s2); for (i = 0; i < len; ++i) printf("%x ",s2[i]); printf("\n"); } void ParseXML(const char* csInput) { XML_Parser parser = XML_ParserCreate("iso- 8859-1"); int len = 0; XML_SetElementHandler(parser, startElement, endElement); XML_SetCharacterDataHandler(parser, characterData); len = strlen(csInput); printf("started XML parse\n"); if (!XML_Parse(parser, csInput, len, 1)) { printf("%s at line %d column %d\n", XML_ErrorString(XML_GetErrorCode (parser)), XML_GetCurrentLineNumber(parser), XML_GetCurrentColumnNumber (parser)); return; } XML_ParserFree(parser); } Any help would be appreciated. Thanks, Tony ---------------------------------------------------------------------- >Comment By: Tony Palmer (etpalmer) Date: 2003-07-09 15:19 Message: Logged In: YES user_id=818598 Thanks for the clarification. I guess then I am not sure how I am supposed to convert from UTF-8 back to the iso-8859-1 character that was passed into the parser. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 20:20 Message: Logged In: YES user_id=290026 Are you aware that Expat reports XML content encoded as UTF-8 or UTF-16 only? The document's encoding is irrelevant for that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=768010&group_id=10127 From noreply at sourceforge.net Wed Jul 9 09:32:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 9 11:32:39 2003 Subject: [Expat-bugs] [ expat-Bugs-768010 ] Extended characters not parsed correctly... Message-ID: Bugs item #768010, was opened at 2003-07-08 16:13 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=768010&group_id=10127 Category: None Group: None >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Tony Palmer (etpalmer) Assigned to: Nobody/Anonymous (nobody) Summary: Extended characters not parsed correctly... Initial Comment: We have been using the expat parser for a couple years and have recently had need for parsing extended characters (128-255). Even though I specify "iso-8859- 1" in my parser create, it still is returning me incorrect character data. I am not sure what I am doing wrong. I am on a window 2000 platform with 1.95.6 now. I feed in the following: T?NY What I get out of the parse is (start,character data, hex of character data, end): MESSAGE T├?NY 54 ffffffc3 ffffff96 4e 59 MESSAGE My code is as follows: void startElement(void *userData, const char *name, const char **atts) { printf("%s\n",name); } void endElement(void *userData, const char *name) { printf("%s\n",name); } void characterData(void *userData, const XML_Char *s, int len) { char s2[256000]; int i; strncpy(s2,s,len); s2[len]=0; printf("%s\n", s2); for (i = 0; i < len; ++i) printf("%x ",s2[i]); printf("\n"); } void ParseXML(const char* csInput) { XML_Parser parser = XML_ParserCreate("iso- 8859-1"); int len = 0; XML_SetElementHandler(parser, startElement, endElement); XML_SetCharacterDataHandler(parser, characterData); len = strlen(csInput); printf("started XML parse\n"); if (!XML_Parse(parser, csInput, len, 1)) { printf("%s at line %d column %d\n", XML_ErrorString(XML_GetErrorCode (parser)), XML_GetCurrentLineNumber(parser), XML_GetCurrentColumnNumber (parser)); return; } XML_ParserFree(parser); } Any help would be appreciated. Thanks, Tony ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-09 11:32 Message: Logged In: YES user_id=290026 It generally makes not much sense to process data internally in a non-standard encoding, as you may have input from various sources with different encodings, and you would have to write different code for each encoding. You likely need to convert to ISO-8859-1 for display and output purposes only. This is easiest if you use the version of Expat that reports wide characters (UTF-16), since ISO-8859-1 is a subset of UTF-16 that can be obtained by simply taking all UTF-16 characters with a zero high-byte, and extract the low-byte. Closing this report, as it is not a bug. ---------------------------------------------------------------------- Comment By: Tony Palmer (etpalmer) Date: 2003-07-09 11:19 Message: Logged In: YES user_id=818598 Thanks for the clarification. I guess then I am not sure how I am supposed to convert from UTF-8 back to the iso-8859-1 character that was passed into the parser. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-08 16:20 Message: Logged In: YES user_id=290026 Are you aware that Expat reports XML content encoded as UTF-8 or UTF-16 only? The document's encoding is irrelevant for that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=768010&group_id=10127 From noreply at sourceforge.net Sun Jul 13 19:13:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jul 13 21:13:25 2003 Subject: [Expat-bugs] [ expat-Bugs-770740 ] Unchecked 'Proper Conditional Section/PE Nesting' Message-ID: Bugs item #770740, was opened at 2003-07-14 01:13 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=770740&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brett Kail (bkail) Assigned to: Nobody/Anonymous (nobody) Summary: Unchecked 'Proper Conditional Section/PE Nesting' Initial Comment: The validity constraint 'Proper Conditional Section/PE Nesting' is apparently not checked: test.xml: %test; ]> test.dtd: "> %begin;INCLUDE[]]> Bugs item #770740, was opened at 2003-07-14 01:13 Message generated for change (Comment added) made by bkail You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770740&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brett Kail (bkail) Assigned to: Nobody/Anonymous (nobody) Summary: Unchecked 'Proper Conditional Section/PE Nesting' Initial Comment: The validity constraint 'Proper Conditional Section/PE Nesting' is apparently not checked: test.xml: %test; ]> test.dtd: "> %begin;INCLUDE[]]> Comment By: Brett Kail (bkail) Date: 2003-07-14 01:17 Message: Logged In: YES user_id=592038 *sigh*, it seems I accidently submitted this before I had finished editing. The version I'm using is: xmlwf using expat_1.95.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770740&group_id=10127 From noreply at sourceforge.net Sun Jul 13 20:44:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jul 13 22:44:25 2003 Subject: [Expat-bugs] [ expat-Bugs-770765 ] why expat-1.95.6 can also NOT parse parameter entity ? Message-ID: Bugs item #770765, was opened at 2003-07-13 19:44 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=770765&group_id=10127 Category: XML::Parser (inactive) Group: Feature Request Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: why expat-1.95.6 can also NOT parse parameter entity ? Initial Comment: Both expat-1.2 and expat-1.95.6 can NOT parse parameter entity. Who can tell me what reason is it for ? Just like the follow sample can NOT pass expat parser: ]> wang.liang@neusoft.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770765&group_id=10127 From noreply at sourceforge.net Mon Jul 14 07:29:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 14 09:32:21 2003 Subject: [Expat-bugs] [ expat-Bugs-770765 ] why expat-1.95.6 can also NOT parse parameter entity ? Message-ID: Bugs item #770765, was opened at 2003-07-14 02:44 Message generated for change (Comment added) made by bkail You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770765&group_id=10127 Category: XML::Parser (inactive) Group: Feature Request Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: why expat-1.95.6 can also NOT parse parameter entity ? Initial Comment: Both expat-1.2 and expat-1.95.6 can NOT parse parameter entity. Who can tell me what reason is it for ? Just like the follow sample can NOT pass expat parser: ]> wang.liang@neusoft.com ---------------------------------------------------------------------- Comment By: Brett Kail (bkail) Date: 2003-07-14 13:29 Message: Logged In: YES user_id=592038 "The external subset and external parameter entities also differ from the internal subset in that in them, parameter- entity references are permitted within markup declarations, not only between markup declarations." Receiving an error for your testcase is required, and therefore, it is not a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770765&group_id=10127 From noreply at sourceforge.net Mon Jul 14 07:40:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 14 09:42:11 2003 Subject: [Expat-bugs] [ expat-Bugs-770740 ] Unchecked 'Proper Conditional Section/PE Nesting' Message-ID: Bugs item #770740, was opened at 2003-07-13 21:13 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770740&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brett Kail (bkail) Assigned to: Nobody/Anonymous (nobody) Summary: Unchecked 'Proper Conditional Section/PE Nesting' Initial Comment: The validity constraint 'Proper Conditional Section/PE Nesting' is apparently not checked: test.xml: %test; ]> test.dtd: "> %begin;INCLUDE[]]> Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-14 09:40 Message: Logged In: YES user_id=290026 If it is a validity constraint then Expat must not check it, since Expat does not validate. ---------------------------------------------------------------------- Comment By: Brett Kail (bkail) Date: 2003-07-13 21:17 Message: Logged In: YES user_id=592038 *sigh*, it seems I accidently submitted this before I had finished editing. The version I'm using is: xmlwf using expat_1.95.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770740&group_id=10127 From noreply at sourceforge.net Mon Jul 14 07:54:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 14 09:54:19 2003 Subject: [Expat-bugs] [ expat-Bugs-770740 ] Unchecked 'Proper Conditional Section/PE Nesting' Message-ID: Bugs item #770740, was opened at 2003-07-13 21:13 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770740&group_id=10127 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Brett Kail (bkail) Assigned to: Nobody/Anonymous (nobody) Summary: Unchecked 'Proper Conditional Section/PE Nesting' Initial Comment: The validity constraint 'Proper Conditional Section/PE Nesting' is apparently not checked: test.xml: %test; ]> test.dtd: "> %begin;INCLUDE[]]> Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-14 09:54 Message: Logged In: YES user_id=3066 This is a validity constraint; see the XML 1.0 specification, section 3.4: http://www.w3.org/TR/REC-xml#sec-condition-sect Closing as Invalid, since this isn't a bug; Expat must not implement this check. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-14 09:40 Message: Logged In: YES user_id=290026 If it is a validity constraint then Expat must not check it, since Expat does not validate. ---------------------------------------------------------------------- Comment By: Brett Kail (bkail) Date: 2003-07-13 21:17 Message: Logged In: YES user_id=592038 *sigh*, it seems I accidently submitted this before I had finished editing. The version I'm using is: xmlwf using expat_1.95.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770740&group_id=10127 From noreply at sourceforge.net Tue Jul 15 07:52:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 09:52:44 2003 Subject: [Expat-bugs] [ expat-Bugs-771612 ] Namespace separator ` won't work? Message-ID: Bugs item #771612, was opened at 2003-07-15 15:52 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=771612&group_id=10127 Category: www.libexpat.org Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wilhelm Koestinger (wkoestin) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Namespace separator ` won't work? Initial Comment: I'm trying to get Sabltron 0.98 and Expat 1.95.5 together with php 4.3.2 working on AIX 5.1. I can compile everthing i need, but get a segmentation fault when running the whole stuff. Analyzing the core dump, i tracked the error down to the function XML_ParserCreateNS(..). I then ran your unit tests, which worked fine. Looking at the Sablotron code, i found out that they are using "`" as namespace character. When i used this character in your unit tests, they failed. Running suite(s): basic 89%: Checks: 29, Failures: 3, Errors: 0 tests/runtests.c:674:F:XML namespaces: unexpected start string: 'http://expat.sf.net/`e`foo' tests/chardata.c:96:F:XML namespaces: got bad data bytes tests/chardata.c:96:F:XML namespaces: got bad data bytes make: *** [check] Error 1 Can you tell me if "`" is not a valid namespace separator? I appriciate any help you can give to me! Thanks, Willi ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 From noreply at sourceforge.net Tue Jul 15 08:50:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 10:50:57 2003 Subject: [Expat-bugs] [ expat-Bugs-771612 ] Namespace separator ` won't work? Message-ID: Bugs item #771612, was opened at 2003-07-15 09:52 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 >Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wilhelm Koestinger (wkoestin) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Namespace separator ` won't work? Initial Comment: I'm trying to get Sabltron 0.98 and Expat 1.95.5 together with php 4.3.2 working on AIX 5.1. I can compile everthing i need, but get a segmentation fault when running the whole stuff. Analyzing the core dump, i tracked the error down to the function XML_ParserCreateNS(..). I then ran your unit tests, which worked fine. Looking at the Sablotron code, i found out that they are using "`" as namespace character. When i used this character in your unit tests, they failed. Running suite(s): basic 89%: Checks: 29, Failures: 3, Errors: 0 tests/runtests.c:674:F:XML namespaces: unexpected start string: 'http://expat.sf.net/`e`foo' tests/chardata.c:96:F:XML namespaces: got bad data bytes tests/chardata.c:96:F:XML namespaces: got bad data bytes make: *** [check] Error 1 Can you tell me if "`" is not a valid namespace separator? I appriciate any help you can give to me! Thanks, Willi ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-15 10:50 Message: Logged In: YES user_id=3066 If you only changed namespace_setup() to use a single quote instead of a space, the strings that encode the expected output no longer match what should be expected. If those are also changed, using ' works fine. Can you try building Sablotron with the current CVS version of Expat? We'd like to release Expat 1.96.7 in the near future, so making sure this version works with Sablotron is important. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 From noreply at sourceforge.net Tue Jul 15 09:42:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 11:42:41 2003 Subject: [Expat-bugs] [ expat-Bugs-732794 ] Build issues on Unix platforms Message-ID: Bugs item #732794, was opened at 2003-05-05 12:49 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=732794&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Karl Waclawek (kwaclaw) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Build issues on Unix platforms Initial Comment: Nelson Beebe reported a few issues while building Expat 1.95.6 on various Unix platforms. Attached as file beebe.txt. ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-15 11:42 Message: Logged In: YES user_id=3066 Added notes about the use of check in README revision 1.24. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=732794&group_id=10127 From noreply at sourceforge.net Tue Jul 15 09:57:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 11:57:15 2003 Subject: [Expat-bugs] [ expat-Bugs-770765 ] why expat-1.95.6 can also NOT parse parameter entity ? Message-ID: Bugs item #770765, was opened at 2003-07-13 22:44 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770765&group_id=10127 Category: XML::Parser (inactive) Group: Feature Request >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: why expat-1.95.6 can also NOT parse parameter entity ? Initial Comment: Both expat-1.2 and expat-1.95.6 can NOT parse parameter entity. Who can tell me what reason is it for ? Just like the follow sample can NOT pass expat parser: ]> wang.liang@neusoft.com ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-15 11:57 Message: Logged In: YES user_id=290026 Closed - not a bug as explained below. ---------------------------------------------------------------------- Comment By: Brett Kail (bkail) Date: 2003-07-14 09:29 Message: Logged In: YES user_id=592038 "The external subset and external parameter entities also differ from the internal subset in that in them, parameter- entity references are permitted within markup declarations, not only between markup declarations." Receiving an error for your testcase is required, and therefore, it is not a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=770765&group_id=10127 From noreply at sourceforge.net Tue Jul 15 09:59:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 11:59:45 2003 Subject: [Expat-bugs] [ expat-Bugs-730947 ] unknown encoding handler... bug? or i'm just stupid? Message-ID: Bugs item #730947, was opened at 2003-05-01 15:04 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=730947&group_id=10127 Category: None Group: None >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: unknown encoding handler... bug? or i'm just stupid? Initial Comment: i have a simple written handler for windows-1250 encoding like this (expat 1.95.5, win32): int encoding_handler(void *data, const char *name, XML_Encoding *info) { int i; if(strcmp(name,"windows-1250")!=0) return 0; for(i=0;i<256;i++) info->map[i] = windows1250[i]; /* windows1250 is windows-1250 to unicode mapping table */ info->data = NULL; info->convert = NULL; info->release = NULL; return 1; } handler was set up using this code: XML_SetUnknownEncodingHandler(parser, encoding_handler, NULL); and when i try to parse this xml file: i get unknown encoding error. maybe i'm crazy but really need help (and no fourum exist, anyway:)) ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-15 11:59 Message: Logged In: YES user_id=290026 Closed due to lack of follow-up by submitter. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-05-01 22:29 Message: Logged In: YES user_id=290026 How is your Expat compiled, for UTF-8 or for UTF-16 (XML_UNICODE_WCHAR_T defined)? Also, check if that file has been saved as "Unicode" in Windows (look at it with a hex editor). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=730947&group_id=10127 From noreply at sourceforge.net Tue Jul 15 10:03:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 12:03:41 2003 Subject: [Expat-bugs] [ expat-Bugs-693747 ] compile problem on HP-UX 11 with expat version > 1.95.4 Message-ID: Bugs item #693747, was opened at 2003-02-26 11:47 Message generated for change (Settings changed) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=693747&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: compile problem on HP-UX 11 with expat version > 1.95.4 Initial Comment: complie problem on HP-UX 11 with expat version > 1.95.4 ---------------------------------------- cc -w -O2 -I./lib -I. -o xmlwf/xmlwf.o -c xmlwf/xmlwf.c cc: "xmlwf/xmlwf.c", line 602: error 1000: Unexpected symbol: "*". cc: error 2017: Cannot recover from earlier errors, terminating. make: *** [xmlwf/xmlwf.o] Error 1 ______________________ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=693747&group_id=10127 From noreply at sourceforge.net Wed Jul 16 03:28:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 16 05:29:01 2003 Subject: [Expat-bugs] [ expat-Bugs-772180 ] Configure should check for 'check' library Message-ID: Bugs item #772180, was opened at 2003-07-16 10:28 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=772180&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ed Avis (epaepa) Assigned to: Greg Stein (gstein) Summary: Configure should check for 'check' library Initial Comment: Building expat-1.95.6 on SunOS 5.8 Generic_108528-15 sun4u sparc SUNW. The configure script ought to test for the 'check' library being installed, perhaps by testing for check.h. Otherwise you get failures later on in the build process (during 'make check') if the library is not present. Since the normal convention is for missing libraries to generate a message during configure, rather than a compile error later on, I hope you can count this as a bug. If the library is not found then certain parts of the package could be disabled from building; i.e., the test suite. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=772180&group_id=10127 From noreply at sourceforge.net Wed Jul 16 06:12:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 16 08:12:35 2003 Subject: [Expat-bugs] [ expat-Bugs-772180 ] Configure should check for 'check' library Message-ID: Bugs item #772180, was opened at 2003-07-16 05:28 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=772180&group_id=10127 Category: Build control Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Ed Avis (epaepa) Assigned to: Greg Stein (gstein) Summary: Configure should check for 'check' library Initial Comment: Building expat-1.95.6 on SunOS 5.8 Generic_108528-15 sun4u sparc SUNW. The configure script ought to test for the 'check' library being installed, perhaps by testing for check.h. Otherwise you get failures later on in the build process (during 'make check') if the library is not present. Since the normal convention is for missing libraries to generate a message during configure, rather than a compile error later on, I hope you can count this as a bug. If the library is not found then certain parts of the package could be disabled from building; i.e., the test suite. ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-16 08:12 Message: Logged In: YES user_id=3066 Duplicate of SF bug #664541. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=772180&group_id=10127 From noreply at sourceforge.net Wed Jul 16 06:19:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 16 08:19:31 2003 Subject: [Expat-bugs] [ expat-Bugs-772180 ] Configure should check for 'check' library Message-ID: Bugs item #772180, was opened at 2003-07-16 10:28 Message generated for change (Comment added) made by epaepa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=772180&group_id=10127 Category: Build control Group: None Status: Closed Resolution: Duplicate Priority: 5 Submitted By: Ed Avis (epaepa) Assigned to: Greg Stein (gstein) Summary: Configure should check for 'check' library Initial Comment: Building expat-1.95.6 on SunOS 5.8 Generic_108528-15 sun4u sparc SUNW. The configure script ought to test for the 'check' library being installed, perhaps by testing for check.h. Otherwise you get failures later on in the build process (during 'make check') if the library is not present. Since the normal convention is for missing libraries to generate a message during configure, rather than a compile error later on, I hope you can count this as a bug. If the library is not found then certain parts of the package could be disabled from building; i.e., the test suite. ---------------------------------------------------------------------- >Comment By: Ed Avis (epaepa) Date: 2003-07-16 13:19 Message: Logged In: YES user_id=10769 Sorry about that - I quite forgot I had submitted the same bug six months ago :-(. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-16 13:12 Message: Logged In: YES user_id=3066 Duplicate of SF bug #664541. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=772180&group_id=10127 From noreply at sourceforge.net Wed Jul 16 06:23:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 16 08:23:20 2003 Subject: [Expat-bugs] [ expat-Bugs-699323 ] VMS: descrip.mms incomplete (1.95.6 et al) Message-ID: Bugs item #699323, was opened at 2003-03-07 06:36 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=699323&group_id=10127 Category: Build control Group: Platform Specific >Status: Pending >Resolution: Accepted Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Fred L. Drake, Jr. (fdrake) Summary: VMS: descrip.mms incomplete (1.95.6 et al) Initial Comment: MMS fails after updating library with: %MMS-F-GWKNOACTS, Actions to update ALL are unknown. Fix: replace the "all : $(library)" line with: "all : sys$common:[syslib]$(LIBRARY), sys$common:[syslib]expat.h @ ! sys$common:[syslib]$(library) : $(library) copy/log $(mms$source) $(mms$target) sys$common:[syslib]expat.h : $(apiheader) copy/log $(mms$source) $(mms$target) " NB: it's important that each rule consists of a 1-line 'dependency' followed by a 1-line 'action' followed by a blank line. The spaces are important too. (Yes, MMS *is* very picky) - chris.sharman@ccagroup.co.uk ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-16 08:23 Message: Logged In: YES user_id=3066 I've applied the patch from berryc as vms/descrip.mms revision 1.2. Please check out the CVS version and confirm that I didn't make any errors; I have no access to a VMS machine (or enough knowledge to make use of one if I did). ---------------------------------------------------------------------- Comment By: Craig A. Berry (berryc) Date: 2003-03-16 16:33 Message: Logged In: YES user_id=717096 The suggested fix is incorrect because it installs the object library and expat.h in a system directory as part of the build process. It's questionable whether a package should ever put its own files in sys$common:[syslib], and if it does, it should do so as part of a separate install step (not currently implemented) and not as part of the initial make. There is nothing wrong with not having an action line, but it does lead to a less than informative message in the case of the "all" target, which exists solely to drive the other dependencies. The patch below is all that's needed to replace that message with something more informative: --- vms/descrip.mms;-0 Tue Jun 4 23:13:10 2002 +++ vms/descrip.mms Sun Mar 16 14:47:46 2003 @@ -40,2 +40,3 @@ all : $(LIBRARY) + @ write sys$output "All made." [end of patch] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=699323&group_id=10127 From noreply at sourceforge.net Wed Jul 16 08:26:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 16 10:27:08 2003 Subject: [Expat-bugs] [ expat-Bugs-771612 ] Namespace separator ` won't work? Message-ID: Bugs item #771612, was opened at 2003-07-15 06:52 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wilhelm Koestinger (wkoestin) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Namespace separator ` won't work? Initial Comment: I'm trying to get Sabltron 0.98 and Expat 1.95.5 together with php 4.3.2 working on AIX 5.1. I can compile everthing i need, but get a segmentation fault when running the whole stuff. Analyzing the core dump, i tracked the error down to the function XML_ParserCreateNS(..). I then ran your unit tests, which worked fine. Looking at the Sablotron code, i found out that they are using "`" as namespace character. When i used this character in your unit tests, they failed. Running suite(s): basic 89%: Checks: 29, Failures: 3, Errors: 0 tests/runtests.c:674:F:XML namespaces: unexpected start string: 'http://expat.sf.net/`e`foo' tests/chardata.c:96:F:XML namespaces: got bad data bytes tests/chardata.c:96:F:XML namespaces: got bad data bytes make: *** [check] Error 1 Can you tell me if "`" is not a valid namespace separator? I appriciate any help you can give to me! Thanks, Willi ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-07-16 07:26 Message: Logged In: NO what iconv are you using? the IBM or gnu version? ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-15 07:50 Message: Logged In: YES user_id=3066 If you only changed namespace_setup() to use a single quote instead of a space, the strings that encode the expected output no longer match what should be expected. If those are also changed, using ' works fine. Can you try building Sablotron with the current CVS version of Expat? We'd like to release Expat 1.96.7 in the near future, so making sure this version works with Sablotron is important. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 From noreply at sourceforge.net Wed Jul 16 08:55:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 16 10:55:20 2003 Subject: [Expat-bugs] [ expat-Bugs-771612 ] Namespace separator ` won't work? Message-ID: Bugs item #771612, was opened at 2003-07-15 15:52 Message generated for change (Comment added) made by wkoestin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 Category: None Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Wilhelm Koestinger (wkoestin) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Namespace separator ` won't work? Initial Comment: I'm trying to get Sabltron 0.98 and Expat 1.95.5 together with php 4.3.2 working on AIX 5.1. I can compile everthing i need, but get a segmentation fault when running the whole stuff. Analyzing the core dump, i tracked the error down to the function XML_ParserCreateNS(..). I then ran your unit tests, which worked fine. Looking at the Sablotron code, i found out that they are using "`" as namespace character. When i used this character in your unit tests, they failed. Running suite(s): basic 89%: Checks: 29, Failures: 3, Errors: 0 tests/runtests.c:674:F:XML namespaces: unexpected start string: 'http://expat.sf.net/`e`foo' tests/chardata.c:96:F:XML namespaces: got bad data bytes tests/chardata.c:96:F:XML namespaces: got bad data bytes make: *** [check] Error 1 Can you tell me if "`" is not a valid namespace separator? I appriciate any help you can give to me! Thanks, Willi ---------------------------------------------------------------------- >Comment By: Wilhelm Koestinger (wkoestin) Date: 2003-07-16 16:55 Message: Logged In: YES user_id=822862 gnu iconv version 1.8 i found some messages on the php-dev mailinglist and the gingerall.cz message archive concering this problem. it seems to be a linker problem on AIX. i was told to link it statically, then it should work. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-07-16 16:26 Message: Logged In: NO what iconv are you using? the IBM or gnu version? ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-15 16:50 Message: Logged In: YES user_id=3066 If you only changed namespace_setup() to use a single quote instead of a space, the strings that encode the expected output no longer match what should be expected. If those are also changed, using ' works fine. Can you try building Sablotron with the current CVS version of Expat? We'd like to release Expat 1.96.7 in the near future, so making sure this version works with Sablotron is important. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 From noreply at sourceforge.net Wed Jul 16 10:25:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 16 12:25:12 2003 Subject: [Expat-bugs] [ expat-Bugs-771612 ] Namespace separator ` won't work? Message-ID: Bugs item #771612, was opened at 2003-07-15 09:52 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 Category: None >Group: Third-party Bug >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Wilhelm Koestinger (wkoestin) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Namespace separator ` won't work? Initial Comment: I'm trying to get Sabltron 0.98 and Expat 1.95.5 together with php 4.3.2 working on AIX 5.1. I can compile everthing i need, but get a segmentation fault when running the whole stuff. Analyzing the core dump, i tracked the error down to the function XML_ParserCreateNS(..). I then ran your unit tests, which worked fine. Looking at the Sablotron code, i found out that they are using "`" as namespace character. When i used this character in your unit tests, they failed. Running suite(s): basic 89%: Checks: 29, Failures: 3, Errors: 0 tests/runtests.c:674:F:XML namespaces: unexpected start string: 'http://expat.sf.net/`e`foo' tests/chardata.c:96:F:XML namespaces: got bad data bytes tests/chardata.c:96:F:XML namespaces: got bad data bytes make: *** [check] Error 1 Can you tell me if "`" is not a valid namespace separator? I appriciate any help you can give to me! Thanks, Willi ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-16 12:25 Message: Logged In: YES user_id=3066 Sounds like this has been determined not to be an Expat problem; closing this report. ---------------------------------------------------------------------- Comment By: Wilhelm Koestinger (wkoestin) Date: 2003-07-16 10:55 Message: Logged In: YES user_id=822862 gnu iconv version 1.8 i found some messages on the php-dev mailinglist and the gingerall.cz message archive concering this problem. it seems to be a linker problem on AIX. i was told to link it statically, then it should work. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-07-16 10:26 Message: Logged In: NO what iconv are you using? the IBM or gnu version? ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-15 10:50 Message: Logged In: YES user_id=3066 If you only changed namespace_setup() to use a single quote instead of a space, the strings that encode the expected output no longer match what should be expected. If those are also changed, using ' works fine. Can you try building Sablotron with the current CVS version of Expat? We'd like to release Expat 1.96.7 in the near future, so making sure this version works with Sablotron is important. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=771612&group_id=10127 From noreply at sourceforge.net Fri Jul 18 07:16:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jul 18 09:16:40 2003 Subject: [Expat-bugs] [ expat-Bugs-676844 ] expat.h compile error: enum XML_Status Message-ID: Bugs item #676844, was opened at 2003-01-29 07:37 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=676844&group_id=10127 Category: Build control Group: None Status: Open Resolution: Fixed Priority: 9 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: expat.h compile error: enum XML_Status Initial Comment: c++ -DHAVE_CONFIG_H -I. -I. -I../../autocfg -g -O2 -c context.cpp -fPIC -DPIC -o .libs/context.lo In file included from parser.h:45, from guard.h:143, from context.cpp:45: /usr/include/expat.h:657: use of enum `XML_Status' without previous declaration /usr/include/expat.h:736: multiple definition of `enum XML_Status' when building sablotron. Hand editing the file to place the def of enum XML_Status before any references to it fixes the problem. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-07-18 06:16 Message: Logged In: NO After I read all this comments, i saw that u were right. : ) I placed the following definitions enum XML_Status { XML_STATUS_ERROR = 0, #define XML_STATUS_ERROR XML_STATUS_ERROR XML_STATUS_OK = 1 #define XML_STATUS_OK XML_STATUS_OK }; at the beginning of the expat.h file, before any call to it, and it compiled succesfully. After this I compiled sablot with no problems. thank u guys ... : ) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-06-19 08:36 Message: Logged In: NO in configure..:: checking XML::Parser perl module... no: documentation requires XML::Parser module and will not be built. checking whether to build under GPL... no checking whether to build the debugger... no checking where to find xml parser... expat (new) checking expat.h usability... no checking expat.h presence... yes configure: WARNING: expat.h: present but cannot be compiled configure: WARNING: expat.h: check for missing prerequisite headers? configure: WARNING: expat.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf@gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for expat.h... yes checking whether expat.h is broken... yes configure: error: You probably have expat version 1.95.6. Please refer to: http://sourceforge.net/tracker/index.php?func=detail&aid=676844&group_id=10127&atid=110127 for a description of the problem. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-05-30 13:47 Message: Logged In: YES user_id=290026 Yes, the file to fix is expat.h. Two things you can do: 1) get the latest expat.h from CVS, or 2) use your editor to search expat.h for the first location where XML_STATUS is used and then move the definition of XML_STATUS to some location before that point. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-05-30 13:26 Message: Logged In: NO I have the same problem has other senders, but the fix is unclear as you did not indicate which file needs fixing (I assume expat.h) or line number to place the def of enum XML_Status. Please assume people are stupid.. checking expat.h usability... no checking expat.h presence... yes configure: WARNING: expat.h: present but cannot be compiled configure: WARNING: expat.h: check for missing prerequisite headers? configure: WARNING: expat.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf@gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for expat.h... yes checking whether expat.h is broken... yes configure: error: You probably have expat version 1.95.6. Please refer to: http://sourceforge.net/tracker/index.php?func=detail&aid=676844&group_id=10127&atid=110127 for a description of the problem. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-05-08 06:18 Message: Logged In: YES user_id=290026 See above - original submission: Hand editing the file to place the def of enum XML_Status before any references to it fixes the problem. ---------------------------------------------------------------------- Comment By: Donche, Pieter (pdon) Date: 2003-05-08 00:20 Message: Logged In: YES user_id=774177 SUN Sparc Enterprise 2170 Solaris 2.8 gcc 3.2 Downloaded expat-1.95.6.tar.gz ./configure, make, make install OK Downloaded Sablot-0.98.tar.gz (Sablotron package, from www.gingerall.com) ./configure says: ... checking expat.h presence... yes expat.h: present but cannot be compiled expat.h: check for missing prerequisite headers? expat.h: proceeding with the preprocessor's result ##-------------------------------------------------## ## Report this to bug-autoconf@gnu.org ## ##-------------------------------------------------## checking for expat.h... yes checking wether expat.h is broken... yes error: You probably have expat version 1.95.6. Please refer to http://sourceforge.net/tracker/index.php? func=detail&aid=676844&group_id=10127&atid=110127 for a description of the problem -- Looked at that web-page. Don't see a solution there. Wath is the solution ? Pieter.Donche@ua.ac.be ---------------------------------------------------------------------- Comment By: Donche, Pieter (pdon) Date: 2003-05-08 00:20 Message: Logged In: YES user_id=774177 SUN Sparc Enterprise 2170 Solaris 2.8 gcc 3.2 Downloaded expat-1.95.6.tar.gz ./configure, make, make install OK Downloaded Sablot-0.98.tar.gz (Sablotron package, from www.gingerall.com) ./configure says: ... checking expat.h presence... yes expat.h: present but cannot be compiled expat.h: check for missing prerequisite headers? expat.h: proceeding with the preprocessor's result ##-------------------------------------------------## ## Report this to bug-autoconf@gnu.org ## ##-------------------------------------------------## checking for expat.h... yes checking wether expat.h is broken... yes error: You probably have expat version 1.95.6. Please refer to http://sourceforge.net/tracker/index.php? func=detail&aid=676844&group_id=10127&atid=110127 for a description of the problem -- Looked at that web-page. Don't see a solution there. Wath is the solution ? Pieter.Donche@ua.ac.be ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-04-16 06:59 Message: Logged In: YES user_id=290026 Changed priority to highest to make it more visible, so that double reporting incidents occur less frequently. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-03-27 02:42 Message: Logged In: NO Same problem and the same fix under Linux and gcc 2.95.2. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-03-07 03:20 Message: Logged In: NO same problem, same fix when building 1.95.6 on vms (just downloaded .tar.gz & processed - got the rpm, but don't know what to do with it - not an archive type I know how to handle on vms, or windows either) - chris.sharman@ccagroup.co.uk ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-02-28 18:03 Message: Logged In: YES user_id=290026 Strange - I had no problems with MS VC++ 6.0. Which service pack level have you applied? ---------------------------------------------------------------------- Comment By: Jacob Levy (jyljyljyl) Date: 2003-02-28 17:35 Message: Logged In: YES user_id=63723 This makes Expat 1.95.6 unusable for people who create libraries that depend on Expat but don't include their own copy of Expat. Sure, I can edit expat.h and fix it, but my users should not be expected to do that. For that reason I'm staying with Expat 1.95.5 until this problem is fixed. It'd be really nice if you could make Expat 1.95.7 soon.. In my case GCC 2.95.2 and VC++ 6.0 are complaining. ---------------------------------------------------------------------- Comment By: Melvyn Sopacua (nyvlem) Date: 2003-02-13 23:56 Message: Logged In: YES user_id=212431 Yes, that works. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-02-06 12:47 Message: Logged In: YES user_id=290026 But current CVS works for you, right? ---------------------------------------------------------------------- Comment By: Melvyn Sopacua (nyvlem) Date: 2003-02-06 12:17 Message: Logged In: YES user_id=212431 > So far only gcc3.2 has complained. Nope: /usr/local/include/expat.h:657: use of enum `XML_Status' without previous declaration /usr/local/include/expat.h:736: multiple definition of `enum XML_Status' gmake[2]: *** [context.lo] Error 1 gmake[2]: Leaving directory `/home/mdev/cvs/sablot/src/engine' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/home/mdev/cvs/sablot/src' gmake: *** [all-recursive] Error 1 $ gcc --version 2.95.3 ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-01-31 06:43 Message: Logged In: YES user_id=290026 It *is* fixed in CVS. Are you sure you checked out the right version, which is expat.h 1.51? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-01-31 02:34 Message: Logged In: NO I just got the same error, already fixed it. But don't understand why it isn't fixed in CVS ? ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-01-29 10:44 Message: Logged In: YES user_id=3066 I've not checked the C89 standard yet, but Expat 1.95.6 is certainly dodgy in this case. ;-( The first draft of the C spec I found online certainly seemed to imply that any use of an incomplete enum is not allowed; I'm not likely to go out and buy a copy of the final spec to check further. ;-) As noted, this has been fixed in CVS. Fixed the summary to better indicate what this report is about, and lowered the priority to get it out of the way for maintainers. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-01-29 07:51 Message: Logged In: YES user_id=290026 So far only gcc3.2 has complained. Not sure if this is a bug, since most compilers accept it, but it has been fixed in CVS already anyway. Set resolution status to fixed, but leave open. There may be other users who would report this as a bug and I want them to see the open report instead of having duplicates created. Assigned to Fred - since he may know more about whether this truly is a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=676844&group_id=10127 From noreply at sourceforge.net Fri Jul 18 20:41:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jul 18 22:41:17 2003 Subject: [Expat-bugs] [ expat-Bugs-774028 ] can't pass parser witch attribute contained char ">" Message-ID: Bugs item #774028, was opened at 2003-07-18 19: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=774028&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: can't pass parser witch attribute contained char ">" Initial Comment: can't pass parser witch attribute contained char ">" like this: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=774028&group_id=10127 From noreply at sourceforge.net Fri Jul 18 22:26:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jul 19 00:26:06 2003 Subject: [Expat-bugs] [ expat-Bugs-774028 ] can't pass parser witch attribute contained char ">" Message-ID: Bugs item #774028, was opened at 2003-07-18 22:41 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=774028&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: can't pass parser witch attribute contained char ">" Initial Comment: can't pass parser witch attribute contained char ">" like this: ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-07-19 00:26 Message: Logged In: YES user_id=290026 Works for me with current Expat. Btw, we don't have an XML::Parser expert currently. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=774028&group_id=10127 From noreply at sourceforge.net Sun Jul 20 23:06:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 21 01:06:22 2003 Subject: [Expat-bugs] [ expat-Bugs-699323 ] VMS: descrip.mms incomplete (1.95.6 et al) Message-ID: Bugs item #699323, was opened at 2003-03-07 11:36 Message generated for change (Comment added) made by berryc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=699323&group_id=10127 Category: Build control Group: Platform Specific Status: Pending Resolution: Accepted Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: VMS: descrip.mms incomplete (1.95.6 et al) Initial Comment: MMS fails after updating library with: %MMS-F-GWKNOACTS, Actions to update ALL are unknown. Fix: replace the "all : $(library)" line with: "all : sys$common:[syslib]$(LIBRARY), sys$common:[syslib]expat.h @ ! sys$common:[syslib]$(library) : $(library) copy/log $(mms$source) $(mms$target) sys$common:[syslib]expat.h : $(apiheader) copy/log $(mms$source) $(mms$target) " NB: it's important that each rule consists of a 1-line 'dependency' followed by a 1-line 'action' followed by a blank line. The spaces are important too. (Yes, MMS *is* very picky) - chris.sharman@ccagroup.co.uk ---------------------------------------------------------------------- Comment By: Craig A. Berry (berryc) Date: 2003-07-21 05:06 Message: Logged In: YES user_id=717096 Thanks, Fred. I've just tested what's in CVS and it builds fine. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-16 12:23 Message: Logged In: YES user_id=3066 I've applied the patch from berryc as vms/descrip.mms revision 1.2. Please check out the CVS version and confirm that I didn't make any errors; I have no access to a VMS machine (or enough knowledge to make use of one if I did). ---------------------------------------------------------------------- Comment By: Craig A. Berry (berryc) Date: 2003-03-16 21:33 Message: Logged In: YES user_id=717096 The suggested fix is incorrect because it installs the object library and expat.h in a system directory as part of the build process. It's questionable whether a package should ever put its own files in sys$common:[syslib], and if it does, it should do so as part of a separate install step (not currently implemented) and not as part of the initial make. There is nothing wrong with not having an action line, but it does lead to a less than informative message in the case of the "all" target, which exists solely to drive the other dependencies. The patch below is all that's needed to replace that message with something more informative: --- vms/descrip.mms;-0 Tue Jun 4 23:13:10 2002 +++ vms/descrip.mms Sun Mar 16 14:47:46 2003 @@ -40,2 +40,3 @@ all : $(LIBRARY) + @ write sys$output "All made." [end of patch] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=699323&group_id=10127 From noreply at sourceforge.net Mon Jul 21 08:02:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 21 10:03:03 2003 Subject: [Expat-bugs] [ expat-Bugs-699323 ] VMS: descrip.mms incomplete (1.95.6 et al) Message-ID: Bugs item #699323, was opened at 2003-03-07 06:36 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=699323&group_id=10127 Category: Build control Group: Platform Specific >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: VMS: descrip.mms incomplete (1.95.6 et al) Initial Comment: MMS fails after updating library with: %MMS-F-GWKNOACTS, Actions to update ALL are unknown. Fix: replace the "all : $(library)" line with: "all : sys$common:[syslib]$(LIBRARY), sys$common:[syslib]expat.h @ ! sys$common:[syslib]$(library) : $(library) copy/log $(mms$source) $(mms$target) sys$common:[syslib]expat.h : $(apiheader) copy/log $(mms$source) $(mms$target) " NB: it's important that each rule consists of a 1-line 'dependency' followed by a 1-line 'action' followed by a blank line. The spaces are important too. (Yes, MMS *is* very picky) - chris.sharman@ccagroup.co.uk ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-21 10:02 Message: Logged In: YES user_id=3066 Great. Closing the bug report. ---------------------------------------------------------------------- Comment By: Craig A. Berry (berryc) Date: 2003-07-21 01:06 Message: Logged In: YES user_id=717096 Thanks, Fred. I've just tested what's in CVS and it builds fine. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-16 08:23 Message: Logged In: YES user_id=3066 I've applied the patch from berryc as vms/descrip.mms revision 1.2. Please check out the CVS version and confirm that I didn't make any errors; I have no access to a VMS machine (or enough knowledge to make use of one if I did). ---------------------------------------------------------------------- Comment By: Craig A. Berry (berryc) Date: 2003-03-16 16:33 Message: Logged In: YES user_id=717096 The suggested fix is incorrect because it installs the object library and expat.h in a system directory as part of the build process. It's questionable whether a package should ever put its own files in sys$common:[syslib], and if it does, it should do so as part of a separate install step (not currently implemented) and not as part of the initial make. There is nothing wrong with not having an action line, but it does lead to a less than informative message in the case of the "all" target, which exists solely to drive the other dependencies. The patch below is all that's needed to replace that message with something more informative: --- vms/descrip.mms;-0 Tue Jun 4 23:13:10 2002 +++ vms/descrip.mms Sun Mar 16 14:47:46 2003 @@ -40,2 +40,3 @@ all : $(LIBRARY) + @ write sys$output "All made." [end of patch] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=699323&group_id=10127 From noreply at sourceforge.net Mon Jul 28 20:20:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 28 22:20:30 2003 Subject: [Expat-bugs] [ expat-Patches-779333 ] DESTDIR support Message-ID: Patches item #779333, was opened at 2003-07-28 19:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779333&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: DESTDIR support Initial Comment: Here is a patch which enables DESTDIR support for expat (useful for package builders) - apply with patch -p1 -u. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779333&group_id=10127 From noreply at sourceforge.net Mon Jul 28 20:23:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 28 22:23:46 2003 Subject: [Expat-bugs] [ expat-Patches-779334 ] DESTDIR support Message-ID: Patches item #779334, was opened at 2003-07-28 21:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779334&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Philip Warren (pkwarren) Assigned to: Nobody/Anonymous (nobody) Summary: DESTDIR support Initial Comment: DESTDIR support for expat (useful for package builders). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779334&group_id=10127 From noreply at sourceforge.net Mon Jul 28 20:31:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 28 22:31:34 2003 Subject: [Expat-bugs] [ expat-Patches-779333 ] DESTDIR support Message-ID: Patches item #779333, was opened at 2003-07-28 22:20 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779333&group_id=10127 >Category: Build Control >Group: Feature Request >Status: Deleted >Resolution: Duplicate Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: DESTDIR support Initial Comment: Here is a patch which enables DESTDIR support for expat (useful for package builders) - apply with patch -p1 -u. ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2003-07-28 22:31 Message: Logged In: YES user_id=3066 Duplicate of patch #779333, but without the patch attached. Marking deleted at the request of the submitter. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779333&group_id=10127 From noreply at sourceforge.net Mon Jul 28 20:32:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 28 22:32:15 2003 Subject: [Expat-bugs] [ expat-Patches-779334 ] DESTDIR support Message-ID: Patches item #779334, was opened at 2003-07-28 22:23 Message generated for change (Settings changed) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779334&group_id=10127 >Category: Build Control >Group: Feature Request Status: Open Resolution: None Priority: 5 Submitted By: Philip Warren (pkwarren) >Assigned to: Greg Stein (gstein) Summary: DESTDIR support Initial Comment: DESTDIR support for expat (useful for package builders). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779334&group_id=10127 From noreply at sourceforge.net Wed Jul 30 02:44:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jul 30 04:45:04 2003 Subject: [Expat-bugs] [ expat-Bugs-780087 ] bad gcc flag when linking library in Soalris 2.8 Message-ID: Bugs item #780087, was opened at 2003-07-30 01:44 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=780087&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: bad gcc flag when linking library in Soalris 2.8 Initial Comment: expat 1.95.5, 1.95.6 When libtool links the lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo into libexpat.la on Solaris 2.8 when using gcc(3.3 or 3.1), libgcc(3.1 or 3.3) and binutils (2.11.2) ,from SunFreeware.com, it includes the '-no- undefined' flag which causes the make to always fail with a "main not found in crt1.o" error. This of course is silly 'coz a library has no 'main', see gcc discusion http://www.geocrawler.com/mail/msg.php3? msg_id=2903632&list=28. Looking at libtools "link" case statement I see it sets "allow_undefined=yes" but this does not translate to the make line. Could this be a problem? When I manually edited the "make" line, removing the flag '-no-undefined' the library was built without error. As this stops expat building from source on the above platform can I sugest that this is considered an urgent bug to be fixed? Of course I could be wrong :-) Here's an example (I've used 1.95.5 to avoid all those regparm warning messages you get in 1.95.6 on Solaris with gcc 3.1/3.3) snip--- Script started on Wed Jul 30 09:41:53 2003 sh-2.03$ cd expat-1.95.5 sh-2.03$ make distclean ; ./configure ; make cd lib && rm -f libexpat.la *.o *.lo && rm -rf .libs _libs cd xmlwf && rm -f xmlwf *.o *.lo && rm -rf .libs _libs cd examples && rm -f elements outline *.o *.lo && rm - rf .libs _libs cd tests && rm -rf .libs runtests runtests.o chardata.o rm -rf .libs libexpat.la find . -name core | xargs rm -f rm -f expat_config.h config.status config.log config.cache libtool rm -f Makefile checking build system type... sparc-sun-solaris2.8 checking host system type... sparc-sun-solaris2.8 checking for gcc... /usr/local/bin/gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/local/bin/gcc accepts -g... yes checking for ld used by GCC... /usr/local/bin/gcc checking if the linker (/usr/local/bin/gcc) is GNU ld... no checking for /usr/local/bin/gcc option to reload object files... -r checking for BSD-compatible nm... /usr/local/bin/nm -B checking whether ln -s works... yes checking how to recognise dependant libraries... pass_all checking command to parse /usr/local/bin/nm -B output... ok checking how to run the C preprocessor... /usr/local/bin/gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for /usr/local/bin/gcc option to produce PIC... - fPIC checking if /usr/local/bin/gcc PIC flag -fPIC works... yes checking if /usr/local/bin/gcc static flag -static works... yes checking if /usr/local/bin/gcc supports -c -o file.o... yes checking if /usr/local/bin/gcc supports -c -o file.lo... yes checking if /usr/local/bin/gcc supports -fno-rtti -fno- exceptions... yes checking whether the linker (/usr/local/bin/gcc) supports shared libraries... ye s checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... solaris2.8 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes creating libtool checking for gcc... (cached) /usr/local/bin/gcc checking whether we are using the GNU C compiler... (cached) yes checking whether /usr/local/bin/gcc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install- sh -c checking whether gcc accepts -fexceptions... yes checking for ANSI C header files... (cached) yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking whether byte ordering is bigendian... yes checking for /usr/local/bin/gcc option to accept ANSI C... none needed checking for an ANSI C-conforming const... yes checking for off_t... yes checking for size_t... yes checking for working memcmp... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking for memmove... yes checking for bcopy... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h /bin/bash ./libtool --silent -- mode=compile /usr/local/bin/gcc -g -O2 -Wall -Wmi ssing-prototypes -Wstrict-prototypes -fexceptions - I./lib -I. -o lib/xmlparse. lo -c lib/xmlparse.c /bin/bash ./libtool --silent -- mode=compile /usr/local/bin/gcc -g -O2 -Wall -Wmi ssing-prototypes -Wstrict-prototypes -fexceptions - I./lib -I. -o lib/xmltok.lo -c lib/xmltok.c /bin/bash ./libtool --silent -- mode=compile /usr/local/bin/gcc -g -O2 -Wall -Wmi ssing-prototypes -Wstrict-prototypes -fexceptions - I./lib -I. -o lib/xmlrole.l o -c lib/xmlrole.c /bin/bash ./libtool --silent -- mode=link /usr/local/bin/gcc -g -O2 -Wall -Wmissi ng-prototypes -Wstrict-prototypes -fexceptions - I./lib -I. -no-undefined -vers ion-info 4:0:4 -rpath /usr/local/lib -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo Undefined first referenced symbol in file main /usr/local/lib/gcc-lib/sparc- sun-solaris2.8/ 3.3/crt1.o ld: fatal: Symbol referencing errors. No output written to .libs/libexpat.so.0.4 .0 collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `libexpat.la' sh-2.03$ exit script done on Wed Jul 30 09:43:53 2003 snip--- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=780087&group_id=10127