From noreply at sourceforge.net Thu Dec 9 21:21:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 9 21:21:33 2004 Subject: [Expat-bugs] [ expat-Bugs-1082427 ] The install target fails to install file expat_external.h Message-ID: Bugs item #1082427, was opened at 2004-12-09 12:21 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=1082427&group_id=10127 Category: Build control Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: The install target fails to install file expat_external.h Initial Comment: The install fails to install the expat_external.h file in the include directory. Configured with: --prefix=/opt/expat-1.95.8 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1082427&group_id=10127 From noreply at sourceforge.net Thu Dec 9 21:39:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 9 21:39:51 2004 Subject: [Expat-bugs] [ expat-Bugs-1082427 ] The install target fails to install file expat_external.h Message-ID: Bugs item #1082427, was opened at 2004-12-09 15:21 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1082427&group_id=10127 Category: Build control Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: The install target fails to install file expat_external.h Initial Comment: The install fails to install the expat_external.h file in the include directory. Configured with: --prefix=/opt/expat-1.95.8 ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-09 15:39 Message: Logged In: YES user_id=290026 Seems like a duplicate of bug #1000112. Fixed in CVS. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1082427&group_id=10127 From noreply at sourceforge.net Tue Dec 14 18:26:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 14 18:26:48 2004 Subject: [Expat-bugs] [ expat-Patches-1057413 ] two small documentation fixes in links Message-ID: Patches item #1057413, was opened at 2004-10-30 13:36 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1057413&group_id=10127 Category: Documentation Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Michal Molhanec (mol1111) Assigned to: Nobody/Anonymous (nobody) Summary: two small documentation fixes in links Initial Comment: There was missing # in the links. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-14 12:26 Message: Logged In: YES user_id=290026 Fixed in reference.html rev. 1.63. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1057413&group_id=10127 From noreply at sourceforge.net Thu Dec 16 12:35:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 16 12:35:29 2004 Subject: [Expat-bugs] [ expat-Bugs-1086365 ] Parsing short documents causes error. Message-ID: Bugs item #1086365, was opened at 2004-12-16 03:35 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=1086365&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Parsing short documents causes error. Initial Comment: When I parse short XML documents (under 322 characters), I get an error message of type XML_ERROR_INVALID_TOKEN. The document seems to be parsed correctly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 From noreply at sourceforge.net Thu Dec 16 12:40:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 16 12:40:32 2004 Subject: [Expat-bugs] [ expat-Bugs-1086365 ] Parsing short documents causes error. Message-ID: Bugs item #1086365, was opened at 2004-12-16 03:35 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Parsing short documents causes error. Initial Comment: When I parse short XML documents (under 322 characters), I get an error message of type XML_ERROR_INVALID_TOKEN. The document seems to be parsed correctly. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 03:40 Message: Logged In: NO On expat-1.95.8 created by expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 From noreply at sourceforge.net Thu Dec 16 12:44:56 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 16 12:44:59 2004 Subject: [Expat-bugs] [ expat-Bugs-1086365 ] Parsing short documents causes error. Message-ID: Bugs item #1086365, was opened at 2004-12-16 03:35 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Parsing short documents causes error. Initial Comment: When I parse short XML documents (under 322 characters), I get an error message of type XML_ERROR_INVALID_TOKEN. The document seems to be parsed correctly. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 03:44 Message: Logged In: NO on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 03:40 Message: Logged In: NO On expat-1.95.8 created by expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 From noreply at sourceforge.net Thu Dec 16 14:53:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 16 14:53:04 2004 Subject: [Expat-bugs] [ expat-Bugs-1086365 ] Parsing short documents causes error. Message-ID: Bugs item #1086365, was opened at 2004-12-16 06:35 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Parsing short documents causes error. Initial Comment: When I parse short XML documents (under 322 characters), I get an error message of type XML_ERROR_INVALID_TOKEN. The document seems to be parsed correctly. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-16 08:53 Message: Logged In: YES user_id=290026 Give us a reproducible example so that we can eliminate user error. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 06:44 Message: Logged In: NO on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 06:40 Message: Logged In: NO On expat-1.95.8 created by expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 From noreply at sourceforge.net Fri Dec 17 19:11:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 19:11:09 2004 Subject: [Expat-bugs] [ expat-Bugs-985235 ] Patch to Makefile.in for installation into DESTDIR Message-ID: Bugs item #985235, was opened at 2004-07-05 03:40 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=985235&group_id=10127 Category: Build control Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Joerg Friedrich (jeff42) Assigned to: Greg Stein (gstein) Summary: Patch to Makefile.in for installation into DESTDIR Initial Comment: Hi, attached you'll find a patch which enables installation into a DESTDIR. (Helps package buiding) Yours, Joerg ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-17 13:10 Message: Logged In: YES user_id=290026 Fixed in Makefile.in rev. 1.48. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=985235&group_id=10127 From noreply at sourceforge.net Fri Dec 17 19:12:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 19:12:08 2004 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 (Comment added) made by kwaclaw 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: Closed >Resolution: Fixed 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). ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-17 13:12 Message: Logged In: YES user_id=290026 Fixed in Makefile.in rev. 1.48. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=779334&group_id=10127 From noreply at sourceforge.net Fri Dec 17 19:31:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 19:32:07 2004 Subject: [Expat-bugs] [ expat-Patches-888879 ] gb2312 encoding handle Message-ID: Patches item #888879, was opened at 2004-02-02 01:15 Message generated for change (Settings changed) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 Category: None Group: None Status: Open >Resolution: Later Priority: 5 Submitted By: hunter,liu (szhunter) Assigned to: Nobody/Anonymous (nobody) Summary: gb2312 encoding handle Initial Comment: an patch for expat that can let expat handle gb2312 encoding xml file. Developer must use Xml_SetUnknowEncodingHandle() to call XML_GbEncodingHandle() ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-07 09:19 Message: Logged In: YES user_id=290026 Thank you for your patch! For now we will leave it as a standalone patch, as we have not yet determined in which way support for additional encodings should be added to Expat. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 From noreply at sourceforge.net Fri Dec 17 19:32:20 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 19:32:25 2004 Subject: [Expat-bugs] [ expat-Patches-987903 ] Add support of OSD_EBCDIC_DF04_1 Message-ID: Patches item #987903, was opened at 2004-07-09 08:09 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=987903&group_id=10127 Category: None Group: None Status: Open >Resolution: Later Priority: 5 Submitted By: Jean-frederic Clere (jfclere) Assigned to: Nobody/Anonymous (nobody) Summary: Add support of OSD_EBCDIC_DF04_1 Initial Comment: The patch allows to parse a document encoded in EBCDIC. OSD_EBCDIC_DF04_1 is an EBCDIC charset used on BS2000 mainframe and registered at IANA (See http://www.iana.org/assignments/character-sets). I am using the patch in APR (Apache Portable Rutime). The patch could be easly adapted to other EBCDIC encoding by changing the include files map_osd_ebcdic_df04_1.h and osd_ebcdic_df04_1.h ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-17 13:32 Message: Logged In: YES user_id=290026 Thank you for your patch! For now we will leave it as a standalone patch, as we have not yet determined in which way support for additional encodings should be added to Expat. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=987903&group_id=10127 From noreply at sourceforge.net Fri Dec 17 19:39:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 19:39:28 2004 Subject: [Expat-bugs] [ expat-Patches-1050446 ] custom allocators with state Message-ID: Patches item #1050446, was opened at 2004-10-19 22:30 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1050446&group_id=10127 Category: None Group: None Status: Open >Resolution: Postponed Priority: 5 Submitted By: Corey Brenner (coreybrenner) Assigned to: Nobody/Anonymous (nobody) Summary: custom allocators with state Initial Comment: It is sometimes necessary to use different memory allocation routines operating on one pool for different kinds of allocation, or to use different pools with one memory allocation routine (for instance, allocating data structures with a fixed-size allocator, and strings from a string heap utilizing a specialized string allocator). I have made a non-intrusive patch to the expat memory-handling suite which should be binary-compatible for those who are dynamic-linking the expat library. This patch allows one to provide "pool-allocation" function pointers, and a void pointer which is passed to the allocation routines as an extra argument, as part of the memory-handling suite structure. For instance: /* my_allocator prototype, wrapper functions */ extern int my_allocator(int op, void** pp, size_t siz, void* pool); void* my_malloc (size_t siz, void* pool) { void* p = NULL; (void) my_allocator(OBTAIN, &p, siz, pool); return p; } void* my_realloc (void* old, size_t siz, void* pool) { (void) my_allocator(RESIZE, &old, siz, pool); return old; } void my_free (void* mem, void* pool) { (void) my_allocator(RETURN, &mem, 0, pool); } /* using it all */ int foo (void* pool) { XML_Memory_Handling_Suite mhs = { /* malloc_fcn */ NULL, /* realloc_fcn */ NULL, /* free_fcn */ NULL, /* pool_malloc_fcn */ my_malloc, /* pool_realloc_fcn */ my_realloc, /* pool_free_fcn */ my_free, /* pool */ NULL }; XML_Parser parser; mhs.pool = pool; parser = XML_Parser_Create_MM(NULL, &mhs, NULL); if (!parser) { die_horribly(); } /* ... */ } Note: XML_Memory_Handling_Suite has changed, but not in a way that will harm older programs which do not see these additions. The memory-using macros provided in this patch first attempt to utilize the old allocators, if present, and then the new ones, so behavior for older programs is consistent. Documentation is updated to reflect the change. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-17 13:39 Message: Logged In: YES user_id=290026 We are thinking of a future API change (after release 2.0) where the memory allocation call-backs would gain an extra parameter similar tothe userData parameter set on the parser. This looks like your proposal, only more generic. One use case we were thinking of is to prevent the "million laughs" attack by monitoting memory usage per parser instance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1050446&group_id=10127 From noreply at sourceforge.net Sun Dec 19 05:08:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 19 05:08:38 2004 Subject: [Expat-bugs] [ expat-Bugs-1086365 ] Parsing short documents causes error. Message-ID: Bugs item #1086365, was opened at 2004-12-16 03:35 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Parsing short documents causes error. Initial Comment: When I parse short XML documents (under 322 characters), I get an error message of type XML_ERROR_INVALID_TOKEN. The document seems to be parsed correctly. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-18 20:08 Message: Logged In: NO I'm terribly sorry. Checking it on your example (elements.dsp) shows no error. Therefore it is "user error". Sorry again! ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-16 05:53 Message: Logged In: YES user_id=290026 Give us a reproducible example so that we can eliminate user error. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 03:44 Message: Logged In: NO on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 03:40 Message: Logged In: NO On expat-1.95.8 created by expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 From noreply at sourceforge.net Sun Dec 19 07:48:53 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 19 07:48:56 2004 Subject: [Expat-bugs] [ expat-Bugs-1086365 ] Parsing short documents causes error. Message-ID: Bugs item #1086365, was opened at 2004-12-16 06:35 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Parsing short documents causes error. Initial Comment: When I parse short XML documents (under 322 characters), I get an error message of type XML_ERROR_INVALID_TOKEN. The document seems to be parsed correctly. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-19 01:48 Message: Logged In: YES user_id=290026 No problem. Closing report. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-18 23:08 Message: Logged In: NO I'm terribly sorry. Checking it on your example (elements.dsp) shows no error. Therefore it is "user error". Sorry again! ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-16 08:53 Message: Logged In: YES user_id=290026 Give us a reproducible example so that we can eliminate user error. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 06:44 Message: Logged In: NO on Expat-1.95.8 created from expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-16 06:40 Message: Logged In: NO On expat-1.95.8 created by expat_win32bin_1_95_8.exe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1086365&group_id=10127 From noreply at sourceforge.net Mon Dec 20 06:16:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 20 06:16:31 2004 Subject: [Expat-bugs] [ expat-Bugs-1088215 ] Inconsistent namespace separator Message-ID: Bugs item #1088215, was opened at 2004-12-20 00:16 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=1088215&group_id=10127 Category: None Group: Test Required Status: Open Resolution: None Priority: 5 Submitted By: Karl Waclawek (kwaclaw) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Inconsistent namespace separator Initial Comment: When the namespace separator is the null character, it will be omitted between uri and local name. However, when namespace triplets are turned on, the namespace separator between local name and prefix is inconsistently treated, sometimes omitted, sometimes not. The attached patch enforces consistent behaviour such that the separator between local name and prefix is never omitted. This is OK because it is an error to use a null separator in the case of namespace triplets, as per the documentation for XML_ParserCreateNS(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1088215&group_id=10127 From noreply at sourceforge.net Mon Dec 20 06:17:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 20 06:17:59 2004 Subject: [Expat-bugs] [ expat-Bugs-1088215 ] Inconsistent namespace separator Message-ID: Bugs item #1088215, was opened at 2004-12-20 00:16 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1088215&group_id=10127 Category: None Group: Test Required Status: Open Resolution: None Priority: 5 Submitted By: Karl Waclawek (kwaclaw) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Inconsistent namespace separator Initial Comment: When the namespace separator is the null character, it will be omitted between uri and local name. However, when namespace triplets are turned on, the namespace separator between local name and prefix is inconsistently treated, sometimes omitted, sometimes not. The attached patch enforces consistent behaviour such that the separator between local name and prefix is never omitted. This is OK because it is an error to use a null separator in the case of namespace triplets, as per the documentation for XML_ParserCreateNS(). ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-20 00:17 Message: Logged In: YES user_id=290026 The patch was applied in xmlparse.c rev. 1.139. Testing required - assigned to Fred. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1088215&group_id=10127 From noreply at sourceforge.net Tue Dec 21 14:49:41 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 21 14:49:45 2004 Subject: [Expat-bugs] [ expat-Bugs-1021776 ] Recursion in macro "parsing", HP 11.0 Message-ID: Bugs item #1021776, was opened at 2004-09-03 05:06 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1021776&group_id=10127 Category: None Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Recursion in macro "parsing", HP 11.0 Initial Comment: uname -a HP-UX hprgs B.11.00 U 9000/800 76745 unlimited-user license ./configure checking build system type... hppa2.0w-hp-hpux11.00 checking host system type... hppa2.0w-hp-hpux11.00 checking for gcc... /usr/ccs/bin/cc 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... no checking whether /usr/ccs/bin/cc accepts -g... yes checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA -RISC[0-9].[0-9]) shared library checking command to parse /usr/bin/nm -p output... ok checking how to run the C preprocessor... /usr/ccs/bin/ cc -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/ccs/bin/cc option to produce PIC... +Z checking if /usr/ccs/bin/cc PIC flag +Z works... yes checking if /usr/ccs/bin/cc static flag -Wl,-a -Wl,archive works... yes checking if /usr/ccs/bin/cc supports -c -o file.o... no checking if we can lock with hard links... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... relink checking whether stripping libraries is possible... no checking dynamic linker characteristics... hpux11.00 dld.sl 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/ccs/bin/cc checking whether we are using the GNU C compiler... (cached) no checking whether /usr/ccs/bin/cc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install- sh -c checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes checking for /usr/ccs/bin/cc option to accept ANSI C... none needed checking for an ANSI C-conforming const... no checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... cat: Cannot open conftest. c: No such file or directory no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h hprgs:#/varios/perl/expat-1.95.8> ./configure checking build system type... hppa2.0w-hp-hpux11.00 checking host system type... hppa2.0w-hp-hpux11.00 checking for gcc... /usr/ccs/bin/cc 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... no checking whether /usr/ccs/bin/cc accepts -g... yes checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA -RISC[0-9].[0-9]) shared library checking command to parse /usr/bin/nm -p output... ok checking how to run the C preprocessor... /usr/ccs/bin/ cc -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/ccs/bin/cc option to produce PIC... +Z checking if /usr/ccs/bin/cc PIC flag +Z works... yes checking if /usr/ccs/bin/cc static flag -Wl,-a -Wl,archive works... yes checking if /usr/ccs/bin/cc supports -c -o file.o... no checking if we can lock with hard links... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... relink checking whether stripping libraries is possible... no checking dynamic linker characteristics... hpux11.00 dld.sl 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/ccs/bin/cc checking whether we are using the GNU C compiler... (cached) no checking whether /usr/ccs/bin/cc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install- sh -c checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes checking for /usr/ccs/bin/cc option to accept ANSI C... none needed checking for an ANSI C-conforming const... no checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h make /bin/sh ./libtool --silent --mode=compile /usr/ccs/ bin/cc -g -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o lib/ xmlparse.lo -c lib/xmlparse.c (Bundled) cc: warning 480: The -g option is available only with the C/ANSI C product; ignored. (Bundled) cc: warning 480: The +Z option is available only with the C/ANSI C product; ignored. cpp: "lib/xmlparse.c", line 855: error 4065: Recursion in macro "parsing". *** Error exit code 1 Stop. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-21 05:49 Message: Logged In: NO I have the same problem?? Steen.brandtmar@ementor.dk ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-09-14 01:55 Message: Logged In: NO I have the same issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1021776&group_id=10127 From noreply at sourceforge.net Tue Dec 21 15:29:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 21 15:29:51 2004 Subject: [Expat-bugs] [ expat-Bugs-1021776 ] Recursion in macro "parsing", HP 11.0 Message-ID: Bugs item #1021776, was opened at 2004-09-03 08:06 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1021776&group_id=10127 Category: None Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Recursion in macro "parsing", HP 11.0 Initial Comment: uname -a HP-UX hprgs B.11.00 U 9000/800 76745 unlimited-user license ./configure checking build system type... hppa2.0w-hp-hpux11.00 checking host system type... hppa2.0w-hp-hpux11.00 checking for gcc... /usr/ccs/bin/cc 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... no checking whether /usr/ccs/bin/cc accepts -g... yes checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA -RISC[0-9].[0-9]) shared library checking command to parse /usr/bin/nm -p output... ok checking how to run the C preprocessor... /usr/ccs/bin/ cc -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/ccs/bin/cc option to produce PIC... +Z checking if /usr/ccs/bin/cc PIC flag +Z works... yes checking if /usr/ccs/bin/cc static flag -Wl,-a -Wl,archive works... yes checking if /usr/ccs/bin/cc supports -c -o file.o... no checking if we can lock with hard links... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... relink checking whether stripping libraries is possible... no checking dynamic linker characteristics... hpux11.00 dld.sl 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/ccs/bin/cc checking whether we are using the GNU C compiler... (cached) no checking whether /usr/ccs/bin/cc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install- sh -c checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes checking for /usr/ccs/bin/cc option to accept ANSI C... none needed checking for an ANSI C-conforming const... no checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... cat: Cannot open conftest. c: No such file or directory no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h hprgs:#/varios/perl/expat-1.95.8> ./configure checking build system type... hppa2.0w-hp-hpux11.00 checking host system type... hppa2.0w-hp-hpux11.00 checking for gcc... /usr/ccs/bin/cc 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... no checking whether /usr/ccs/bin/cc accepts -g... yes checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA -RISC[0-9].[0-9]) shared library checking command to parse /usr/bin/nm -p output... ok checking how to run the C preprocessor... /usr/ccs/bin/ cc -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/ccs/bin/cc option to produce PIC... +Z checking if /usr/ccs/bin/cc PIC flag +Z works... yes checking if /usr/ccs/bin/cc static flag -Wl,-a -Wl,archive works... yes checking if /usr/ccs/bin/cc supports -c -o file.o... no checking if we can lock with hard links... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... relink checking whether stripping libraries is possible... no checking dynamic linker characteristics... hpux11.00 dld.sl 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/ccs/bin/cc checking whether we are using the GNU C compiler... (cached) no checking whether /usr/ccs/bin/cc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install- sh -c checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes checking for /usr/ccs/bin/cc option to accept ANSI C... none needed checking for an ANSI C-conforming const... no checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h make /bin/sh ./libtool --silent --mode=compile /usr/ccs/ bin/cc -g -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o lib/ xmlparse.lo -c lib/xmlparse.c (Bundled) cc: warning 480: The -g option is available only with the C/ANSI C product; ignored. (Bundled) cc: warning 480: The +Z option is available only with the C/ANSI C product; ignored. cpp: "lib/xmlparse.c", line 855: error 4065: Recursion in macro "parsing". *** Error exit code 1 Stop. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-21 09:29 Message: Logged In: YES user_id=290026 Must be a platform issue, but I have no expertise in it. However, we may get a build expert on board, and then I'll assign this issue to him. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-21 08:49 Message: Logged In: NO I have the same problem?? Steen.brandtmar@ementor.dk ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-09-14 04:55 Message: Logged In: NO I have the same issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1021776&group_id=10127 From noreply at sourceforge.net Tue Dec 21 17:12:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 21 17:12:31 2004 Subject: [Expat-bugs] [ expat-Bugs-1021776 ] Recursion in macro "parsing", HP 11.0 Message-ID: Bugs item #1021776, was opened at 2004-09-03 08:06 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1021776&group_id=10127 Category: None Group: Platform Specific Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Recursion in macro "parsing", HP 11.0 Initial Comment: uname -a HP-UX hprgs B.11.00 U 9000/800 76745 unlimited-user license ./configure checking build system type... hppa2.0w-hp-hpux11.00 checking host system type... hppa2.0w-hp-hpux11.00 checking for gcc... /usr/ccs/bin/cc 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... no checking whether /usr/ccs/bin/cc accepts -g... yes checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA -RISC[0-9].[0-9]) shared library checking command to parse /usr/bin/nm -p output... ok checking how to run the C preprocessor... /usr/ccs/bin/ cc -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/ccs/bin/cc option to produce PIC... +Z checking if /usr/ccs/bin/cc PIC flag +Z works... yes checking if /usr/ccs/bin/cc static flag -Wl,-a -Wl,archive works... yes checking if /usr/ccs/bin/cc supports -c -o file.o... no checking if we can lock with hard links... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... relink checking whether stripping libraries is possible... no checking dynamic linker characteristics... hpux11.00 dld.sl 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/ccs/bin/cc checking whether we are using the GNU C compiler... (cached) no checking whether /usr/ccs/bin/cc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install- sh -c checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes checking for /usr/ccs/bin/cc option to accept ANSI C... none needed checking for an ANSI C-conforming const... no checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... cat: Cannot open conftest. c: No such file or directory no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h hprgs:#/varios/perl/expat-1.95.8> ./configure checking build system type... hppa2.0w-hp-hpux11.00 checking host system type... hppa2.0w-hp-hpux11.00 checking for gcc... /usr/ccs/bin/cc 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... no checking whether /usr/ccs/bin/cc accepts -g... yes checking for non-GNU ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA -RISC[0-9].[0-9]) shared library checking command to parse /usr/bin/nm -p output... ok checking how to run the C preprocessor... /usr/ccs/bin/ cc -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/ccs/bin/cc option to produce PIC... +Z checking if /usr/ccs/bin/cc PIC flag +Z works... yes checking if /usr/ccs/bin/cc static flag -Wl,-a -Wl,archive works... yes checking if /usr/ccs/bin/cc supports -c -o file.o... no checking if we can lock with hard links... yes checking whether the linker (/usr/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... relink checking whether stripping libraries is possible... no checking dynamic linker characteristics... hpux11.00 dld.sl 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/ccs/bin/cc checking whether we are using the GNU C compiler... (cached) no checking whether /usr/ccs/bin/cc accepts -g... (cached) yes checking for a BSD-compatible install... conftools/install- sh -c checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... yes checking for /usr/ccs/bin/cc option to accept ANSI C... none needed checking for an ANSI C-conforming const... no checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h make /bin/sh ./libtool --silent --mode=compile /usr/ccs/ bin/cc -g -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o lib/ xmlparse.lo -c lib/xmlparse.c (Bundled) cc: warning 480: The -g option is available only with the C/ANSI C product; ignored. (Bundled) cc: warning 480: The +Z option is available only with the C/ANSI C product; ignored. cpp: "lib/xmlparse.c", line 855: error 4065: Recursion in macro "parsing". *** Error exit code 1 Stop. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-21 11:12 Message: Logged In: YES user_id=290026 I had a further look at the source and found these macros #define parsing (parser->m_parsingStatus.parsing) #define finalBuffer (parser->m_parsingStatus.finalBuffer) as the likely source of your problems. AFAIK, if a macro refers to itself, then the C preprocessor must not expand the reference, so it looks as if your compiler breaks that rule. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-21 09:29 Message: Logged In: YES user_id=290026 Must be a platform issue, but I have no expertise in it. However, we may get a build expert on board, and then I'll assign this issue to him. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-21 08:49 Message: Logged In: NO I have the same problem?? Steen.brandtmar@ementor.dk ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-09-14 04:55 Message: Logged In: NO I have the same issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1021776&group_id=10127 From noreply at sourceforge.net Tue Dec 21 19:24:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 21 19:24:25 2004 Subject: [Expat-bugs] [ expat-Patches-1050446 ] custom allocators with state Message-ID: Patches item #1050446, was opened at 2004-10-19 19:30 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1050446&group_id=10127 Category: None Group: None Status: Open Resolution: Postponed Priority: 5 Submitted By: Corey Brenner (coreybrenner) Assigned to: Nobody/Anonymous (nobody) Summary: custom allocators with state Initial Comment: It is sometimes necessary to use different memory allocation routines operating on one pool for different kinds of allocation, or to use different pools with one memory allocation routine (for instance, allocating data structures with a fixed-size allocator, and strings from a string heap utilizing a specialized string allocator). I have made a non-intrusive patch to the expat memory-handling suite which should be binary-compatible for those who are dynamic-linking the expat library. This patch allows one to provide "pool-allocation" function pointers, and a void pointer which is passed to the allocation routines as an extra argument, as part of the memory-handling suite structure. For instance: /* my_allocator prototype, wrapper functions */ extern int my_allocator(int op, void** pp, size_t siz, void* pool); void* my_malloc (size_t siz, void* pool) { void* p = NULL; (void) my_allocator(OBTAIN, &p, siz, pool); return p; } void* my_realloc (void* old, size_t siz, void* pool) { (void) my_allocator(RESIZE, &old, siz, pool); return old; } void my_free (void* mem, void* pool) { (void) my_allocator(RETURN, &mem, 0, pool); } /* using it all */ int foo (void* pool) { XML_Memory_Handling_Suite mhs = { /* malloc_fcn */ NULL, /* realloc_fcn */ NULL, /* free_fcn */ NULL, /* pool_malloc_fcn */ my_malloc, /* pool_realloc_fcn */ my_realloc, /* pool_free_fcn */ my_free, /* pool */ NULL }; XML_Parser parser; mhs.pool = pool; parser = XML_Parser_Create_MM(NULL, &mhs, NULL); if (!parser) { die_horribly(); } /* ... */ } Note: XML_Memory_Handling_Suite has changed, but not in a way that will harm older programs which do not see these additions. The memory-using macros provided in this patch first attempt to utilize the old allocators, if present, and then the new ones, so behavior for older programs is consistent. Documentation is updated to reflect the change. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-21 10:24 Message: Logged In: NO Did my patch not make it through? I did submit one. If not, please allow me to email it to someone. My patch does this without breaking the 1.9x API, so it can be used currently. Thanks, --Corey ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-17 10:39 Message: Logged In: YES user_id=290026 We are thinking of a future API change (after release 2.0) where the memory allocation call-backs would gain an extra parameter similar tothe userData parameter set on the parser. This looks like your proposal, only more generic. One use case we were thinking of is to prevent the "million laughs" attack by monitoting memory usage per parser instance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1050446&group_id=10127 From noreply at sourceforge.net Tue Dec 21 19:32:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 21 19:32:28 2004 Subject: [Expat-bugs] [ expat-Bugs-972802 ] Xml document which begin with an empty line Message-ID: Bugs item #972802, was opened at 2004-06-14 16:51 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=972802&group_id=10127 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Karl Waclawek (kwaclaw) Summary: Xml document which begin with an empty line Initial Comment: In a xml document which begins with an empty line, for example: """Start here""" """End here""" Expat give this parse error: XML Parsing Error: xml processing instruction not at start of external entity. I discoverd this bug when I tried to pass an xhtml document to firefox via ASP.NET with the "application/xhtml+xml" content-type. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-21 13:32 Message: Logged In: YES user_id=290026 Changed error message to: "XML or text declaration not at start of entity". Applied in xmlparse.c rev. 1 140. Closing this issue. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-08-04 11:52 Message: Logged In: YES user_id=290026 Let's leave this as an improvement for release 2.0. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2004-07-23 00:06 Message: Logged In: YES user_id=3066 Karl, did you want to do anything with this for 1.95.8? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-06-15 08:55 Message: Logged In: YES user_id=290026 >From the XML spec: [1] document ::= prolog element Misc* [22] prolog ::= XMLDecl? Misc* (doctypedecl Misc*)? [23] XMLDecl ::= '' Which means that it is an error if an XML document starts with an empty line. So Expat is OK. However, Expat's error message could be improved to say: "XML/Text declaration not at start of external entity". So maybe we should change the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=972802&group_id=10127 From noreply at sourceforge.net Tue Dec 21 19:35:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 21 19:35:35 2004 Subject: [Expat-bugs] [ expat-Patches-1050446 ] custom allocators with state Message-ID: Patches item #1050446, was opened at 2004-10-19 22:30 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1050446&group_id=10127 Category: None Group: None Status: Open Resolution: Postponed Priority: 5 Submitted By: Corey Brenner (coreybrenner) Assigned to: Nobody/Anonymous (nobody) Summary: custom allocators with state Initial Comment: It is sometimes necessary to use different memory allocation routines operating on one pool for different kinds of allocation, or to use different pools with one memory allocation routine (for instance, allocating data structures with a fixed-size allocator, and strings from a string heap utilizing a specialized string allocator). I have made a non-intrusive patch to the expat memory-handling suite which should be binary-compatible for those who are dynamic-linking the expat library. This patch allows one to provide "pool-allocation" function pointers, and a void pointer which is passed to the allocation routines as an extra argument, as part of the memory-handling suite structure. For instance: /* my_allocator prototype, wrapper functions */ extern int my_allocator(int op, void** pp, size_t siz, void* pool); void* my_malloc (size_t siz, void* pool) { void* p = NULL; (void) my_allocator(OBTAIN, &p, siz, pool); return p; } void* my_realloc (void* old, size_t siz, void* pool) { (void) my_allocator(RESIZE, &old, siz, pool); return old; } void my_free (void* mem, void* pool) { (void) my_allocator(RETURN, &mem, 0, pool); } /* using it all */ int foo (void* pool) { XML_Memory_Handling_Suite mhs = { /* malloc_fcn */ NULL, /* realloc_fcn */ NULL, /* free_fcn */ NULL, /* pool_malloc_fcn */ my_malloc, /* pool_realloc_fcn */ my_realloc, /* pool_free_fcn */ my_free, /* pool */ NULL }; XML_Parser parser; mhs.pool = pool; parser = XML_Parser_Create_MM(NULL, &mhs, NULL); if (!parser) { die_horribly(); } /* ... */ } Note: XML_Memory_Handling_Suite has changed, but not in a way that will harm older programs which do not see these additions. The memory-using macros provided in this patch first attempt to utilize the old allocators, if present, and then the new ones, so behavior for older programs is consistent. Documentation is updated to reflect the change. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-21 13:35 Message: Logged In: YES user_id=290026 We are leaving your patch as a standalone patch for the moment, since - as already mentioned - we are thinking of doing something similar, but somewhat different, for a post 2.0 release. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-21 13:24 Message: Logged In: NO Did my patch not make it through? I did submit one. If not, please allow me to email it to someone. My patch does this without breaking the 1.9x API, so it can be used currently. Thanks, --Corey ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-17 13:39 Message: Logged In: YES user_id=290026 We are thinking of a future API change (after release 2.0) where the memory allocation call-backs would gain an extra parameter similar tothe userData parameter set on the parser. This looks like your proposal, only more generic. One use case we were thinking of is to prevent the "million laughs" attack by monitoting memory usage per parser instance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=1050446&group_id=10127 From noreply at sourceforge.net Thu Dec 23 02:20:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 23 02:20:05 2004 Subject: [Expat-bugs] [ expat-Patches-460042 ] fix XML_SetReturnNSTriplet Message-ID: Patches item #460042, was opened at 2001-09-09 10:15 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=460042&group_id=10127 Category: None Group: None Status: Closed Resolution: Rejected Priority: 5 Submitted By: TAKAHASHI Masayoshi (maki) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: fix XML_SetReturnNSTriplet Initial Comment: This is a patch for lib/xmlparser.c, to fix XML_SetReturnNSTriplet. It may be solved "[#231864] XML_SetReturnNSTriplet doesn't work as documented". This patch is written by yoshidam. He writes Ruby's expat library 'XMLParser'. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-22 17:20 Message: Logged In: NO What is the contest of these two files? photoSchema.xml digSchema.xml ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-04-19 14:01 Message: Logged In: YES user_id=3066 The bug this addresses is now closed. An alternate version of this patch was used; see SF patch #476929. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2001-09-25 10:09 Message: Logged In: YES user_id=290026 I have applied the patch, and it seem to work with the compile options as installed (release 1.95.2 for Win32). However, if I recompile with XML_UNICODE and XML_UNICODE_WCHAR_T defined, the last (third) element was not returned in my test example: ... <cameras xmlns:dig="x-schema:digSchema.xml" xmlns:photo="x-schema:photoSchema.xml"> <dig:camera prodID="P663" name="Click-N-Go Camera" pixels="410000" output_res="640 x 480" int_mem="2 MB" price="300.99"/> ... with the namespace separator '^', the patched code returns the element name 'x-schema:digSchema.xml^camera', instead of 'x-schema:digSchema.xml^camera^dig:camera'. Karl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=460042&group_id=10127 From noreply at sourceforge.net Thu Dec 23 02:22:11 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 23 02:22:14 2004 Subject: [Expat-bugs] [ expat-Patches-460042 ] fix XML_SetReturnNSTriplet Message-ID: Patches item #460042, was opened at 2001-09-09 10:15 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=460042&group_id=10127 Category: None Group: None Status: Closed Resolution: Rejected Priority: 5 Submitted By: TAKAHASHI Masayoshi (maki) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: fix XML_SetReturnNSTriplet Initial Comment: This is a patch for lib/xmlparser.c, to fix XML_SetReturnNSTriplet. It may be solved "[#231864] XML_SetReturnNSTriplet doesn't work as documented". This patch is written by yoshidam. He writes Ruby's expat library 'XMLParser'. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-22 17:22 Message: Logged In: NO photoSchema.xml digSchema.xml Thanks busyrushy@hotmail.com ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-12-22 17:20 Message: Logged In: NO What is the contest of these two files? photoSchema.xml digSchema.xml ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-04-19 14:01 Message: Logged In: YES user_id=3066 The bug this addresses is now closed. An alternate version of this patch was used; see SF patch #476929. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2001-09-25 10:09 Message: Logged In: YES user_id=290026 I have applied the patch, and it seem to work with the compile options as installed (release 1.95.2 for Win32). However, if I recompile with XML_UNICODE and XML_UNICODE_WCHAR_T defined, the last (third) element was not returned in my test example: ... <cameras xmlns:dig="x-schema:digSchema.xml" xmlns:photo="x-schema:photoSchema.xml"> <dig:camera prodID="P663" name="Click-N-Go Camera" pixels="410000" output_res="640 x 480" int_mem="2 MB" price="300.99"/> ... with the namespace separator '^', the patched code returns the element name 'x-schema:digSchema.xml^camera', instead of 'x-schema:digSchema.xml^camera^dig:camera'. Karl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=460042&group_id=10127 From noreply at sourceforge.net Fri Dec 24 17:19:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 24 17:19:10 2004 Subject: [Expat-bugs] [ expat-Bugs-1090885 ] Problem with Suspend/Resume mechanism Message-ID: Bugs item #1090885, was opened at 2004-12-24 17:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1090885&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peter Van der Beken (peter_vdb) Assigned to: Nobody/Anonymous (nobody) Summary: Problem with Suspend/Resume mechanism Initial Comment: I block the parser and there is still some data left in the buffer, that data is not the last data of the XML file and it ends on a partial token (" Bugs item #1090885, was opened at 2004-12-24 17:19 Message generated for change (Settings changed) made by peter_vdb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1090885&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peter Van der Beken (peter_vdb) >Assigned to: Karl Waclawek (kwaclaw) Summary: Problem with Suspend/Resume mechanism Initial Comment: I block the parser and there is still some data left in the buffer, that data is not the last data of the XML file and it ends on a partial token (" Bugs item #1090885, was opened at 2004-12-24 11:19 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1090885&group_id=10127 Category: None >Group: Test Required Status: Open >Resolution: Fixed Priority: 5 Submitted By: Peter Van der Beken (peter_vdb) >Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Problem with Suspend/Resume mechanism Initial Comment: I block the parser and there is still some data left in the buffer, that data is not the last data of the XML file and it ends on a partial token ("Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-24 11:32 Message: Logged In: YES user_id=290026 Fixed in xml_parse.c 1.141. Thanks for reporting this, Peter. Leaving it open for testing. Assigned to Fred. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1090885&group_id=10127 From noreply at sourceforge.net Fri Dec 24 19:02:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 24 19:02:58 2004 Subject: [Expat-bugs] [ expat-Bugs-695407 ] Reserved prefixes and namespace names Message-ID: Bugs item #695407, was opened at 2003-02-28 20:46 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=695407&group_id=10127 Category: None >Group: Test Required Status: Open >Resolution: Fixed Priority: 3 Submitted By: Karl Waclawek (kwaclaw) >Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Reserved prefixes and namespace names Initial Comment: Expat does not reject illegal declarations for reserved prefixes and namespace names. From the errata for the Namespaces in XML 1.0 specs: <quote> The prefix xml is by definition bound to the namespace name http://www.w3.org/XML/1998/namespace. It may, but need not, be declared, and must not be bound to any other namespace name. No other prefix may be bound to this namespace name. The prefix xmlns is used only to declare namespace bindings and is by definition bound to the namespace name http://www.w3.org/2000/xmlns/. It must not be declared. No other prefix may be bound to this namespace name. </quote> The following four not-well-formed documents are not rejected by Expat: <?xml version="1.0"?> <!-- Reserved prefixes and namespaces: declaring the xml prefix incorrectly --> <foo xmlns:xml="http://example.org/namespace"/> <?xml version="1.0"?> <!-- Reserved prefixes and namespaces: binding another prefix to the xml namespace --> <foo xmlns:yml="http://www.w3.org/XML/1998/namespace"/> <?xml version="1.0"?> <!-- Reserved prefixes and namespaces: declaring the xmlns prefix with its correct URI (illegal) --> <foo xmlns:xmlns="http://www.w3.org/2000/xmlns/"/> <?xml version="1.0"?> <!-- Reserved prefixes and namespaces: declaring the xmlns prefix with an incorrect URI --> <foo xmlns:xmlns="http://example.org/namespace"/> ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-12-24 13:02 Message: Logged In: YES user_id=290026 Finally fixed in expat.h rev. 1.75 and xmlparse.c rev. 1.142. Fix contributed by Peter van der Beken. Thank you, Peter. We should be very close to passing all test cases in the XML-Test-Suite. Left open for regression test case. Assigned to Fred. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-03-13 08:26 Message: Logged In: YES user_id=290026 Lowered priority to 3. This bug really doesn't have much impact in practical applications, but fixing it may add noticeable overhead. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=695407&group_id=10127 From noreply at sourceforge.net Wed Dec 29 13:43:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 29 13:43:11 2004 Subject: [Expat-bugs] [ expat-Bugs-487387 ] Link Error while in Expat. Message-ID: Bugs item #487387, was opened at 2001-11-30 05:03 Message generated for change (Comment added) made by matt-beard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=487387&group_id=10127 Category: Build control Group: None Status: Closed Resolution: Duplicate Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Link Error while in Expat. Initial Comment: I am trying to install XML::Parser which uses Expat. I installes expat using expat_win32bin_1_95_2.exe. When I try to build XML::Parser, I get a few errors(Error message given Below). I am using Microsoft VC++ Version 6.0 to compile. Perl was built from Source(Version 5.6.1) and is not activestate perl. What could be wrong?? Error Message: Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. cl -c -nologo -O1 -MD -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT -DPERL_MSVCRT_READFIX -O1 -MD -DNDEBUG -DVERSION=\"2.30\" -DXS_VERSION=\"2.30\" -ID:\perl\5.6.1\lib\MSWin32-x86Expat.c "Running Mkbootstrap for XML::Parser::Expat ()" D:\perl\5.6.1\bin\MSWin32-x86\perl.exe -Id:\perl\5.6.1\lib\MSWin32-x86 -Id:\perl\5.6.1\lib -MExtUtils::Command -e chmod 644 Expat.bs link -out:..\blib\arch\auto\XML\Parser\Expat\Expat.dll -dll -nologo -nodefaultlib -release -libpath:"d:\perl\5.6.1\lib\MSWin32-x86\CORE" -machine:x86 Expat.obj D:\perl\5.6.1\li ~1\MICROS~3\VC98\lib\advapi32.lib C:\PROGRA~1\MICROS~3\VC98\lib\shell32.lib C:\PROGRA~1\MICROS~3\VC98\lib\ole32.lib C:\PROGRA~1\MICROS~3\VC98\lib\oleaut32.lib C:\PROGRA~1\MICROS~3\VC98\lib 32.lib C:\PROGRA~1\MICROS~3\VC98\lib\msvcrt.lib -def:Expat.def Creating library ..\blib\arch\auto\XML\Parser\Expat\Expat.lib and object ..\blib\arch\auto\XML\Parser\Expat\Expat.exp Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetParamEntityParsing Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetUnknownEncodingHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetElementHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetUserData Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetNamespaceDeclHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ParserCreate_MM Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetExternalEntityRefHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetNotationDeclHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetUnparsedEntityDeclHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetCdataSectionHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetCommentHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetProcessingInstructionHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetCharacterDataHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ParserFree Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetBase Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetBase Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ExternalEntityParserCreate Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetCurrentLineNumber Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetCurrentColumnNumber Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetCurrentByteIndex Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ErrorString Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetErrorCode Expat.obj : error LNK2001: unresolved external symbol __imp__XML_Parse Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ParseBuffer Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetBuffer ---------------------------------------------------------------------- Comment By: Matt Beard (matt-beard) Date: 2004-12-29 12:43 Message: Logged In: YES user_id=613688 This is NOT a duplicate of bug #432456 - that bug is a problem caused by different DLL versions ending up with the same name. This bug is a problem when trying to link with a STATIC LIBRARY - not at all related to DLL names. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-04-19 21:51 Message: Logged In: YES user_id=3066 This appears to be a duplicate of bug #432456. See the comments in that report for more explanation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=487387&group_id=10127 From noreply at sourceforge.net Wed Dec 29 13:47:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 29 13:47:14 2004 Subject: [Expat-bugs] [ expat-Bugs-487387 ] Link Error while in Expat. Message-ID: Bugs item #487387, was opened at 2001-11-30 05:03 Message generated for change (Comment added) made by matt-beard You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=487387&group_id=10127 Category: Build control Group: None Status: Closed Resolution: Duplicate Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Greg Stein (gstein) Summary: Link Error while in Expat. Initial Comment: I am trying to install XML::Parser which uses Expat. I installes expat using expat_win32bin_1_95_2.exe. When I try to build XML::Parser, I get a few errors(Error message given Below). I am using Microsoft VC++ Version 6.0 to compile. Perl was built from Source(Version 5.6.1) and is not activestate perl. What could be wrong?? Error Message: Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. cl -c -nologo -O1 -MD -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT -DPERL_MSVCRT_READFIX -O1 -MD -DNDEBUG -DVERSION=\"2.30\" -DXS_VERSION=\"2.30\" -ID:\perl\5.6.1\lib\MSWin32-x86Expat.c "Running Mkbootstrap for XML::Parser::Expat ()" D:\perl\5.6.1\bin\MSWin32-x86\perl.exe -Id:\perl\5.6.1\lib\MSWin32-x86 -Id:\perl\5.6.1\lib -MExtUtils::Command -e chmod 644 Expat.bs link -out:..\blib\arch\auto\XML\Parser\Expat\Expat.dll -dll -nologo -nodefaultlib -release -libpath:"d:\perl\5.6.1\lib\MSWin32-x86\CORE" -machine:x86 Expat.obj D:\perl\5.6.1\li ~1\MICROS~3\VC98\lib\advapi32.lib C:\PROGRA~1\MICROS~3\VC98\lib\shell32.lib C:\PROGRA~1\MICROS~3\VC98\lib\ole32.lib C:\PROGRA~1\MICROS~3\VC98\lib\oleaut32.lib C:\PROGRA~1\MICROS~3\VC98\lib 32.lib C:\PROGRA~1\MICROS~3\VC98\lib\msvcrt.lib -def:Expat.def Creating library ..\blib\arch\auto\XML\Parser\Expat\Expat.lib and object ..\blib\arch\auto\XML\Parser\Expat\Expat.exp Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetParamEntityParsing Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetUnknownEncodingHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetElementHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetUserData Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetNamespaceDeclHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ParserCreate_MM Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetExternalEntityRefHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetNotationDeclHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetUnparsedEntityDeclHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetCdataSectionHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetCommentHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetProcessingInstructionHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetCharacterDataHandler Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ParserFree Expat.obj : error LNK2001: unresolved external symbol __imp__XML_SetBase Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetBase Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ExternalEntityParserCreate Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetCurrentLineNumber Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetCurrentColumnNumber Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetCurrentByteIndex Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ErrorString Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetErrorCode Expat.obj : error LNK2001: unresolved external symbol __imp__XML_Parse Expat.obj : error LNK2001: unresolved external symbol __imp__XML_ParseBuffer Expat.obj : error LNK2001: unresolved external symbol __imp__XML_GetBuffer ---------------------------------------------------------------------- Comment By: Matt Beard (matt-beard) Date: 2004-12-29 12:47 Message: Logged In: YES user_id=613688 Oops - please ignore my previous comment!! Posted to the wrong bug!! ---------------------------------------------------------------------- Comment By: Matt Beard (matt-beard) Date: 2004-12-29 12:43 Message: Logged In: YES user_id=613688 This is NOT a duplicate of bug #432456 - that bug is a problem caused by different DLL versions ending up with the same name. This bug is a problem when trying to link with a STATIC LIBRARY - not at all related to DLL names. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-04-19 21:51 Message: Logged In: YES user_id=3066 This appears to be a duplicate of bug #432456. See the comments in that report for more explanation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=487387&group_id=10127