From boby_jose@yahoo.com Tue May 7 23:19:01 2002 From: boby_jose@yahoo.com (boby jose) Date: Tue May 7 22:19:01 2002 Subject: [Expat-discuss] New user Message-ID: <20020508051820.81290.qmail@web10806.mail.yahoo.com> Hi, I have written a XML parser that is working fine. But if I want to use "&", "<", """ and ">". How can I do? thanks, Boby Jose __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com From Axel.Kittenberger@maxxio.com Tue May 7 23:45:04 2002 From: Axel.Kittenberger@maxxio.com (Axel Kittenberger) Date: Tue May 7 22:45:04 2002 Subject: [Expat-discuss] New user In-Reply-To: <20020508051820.81290.qmail@web10806.mail.yahoo.com> References: <20020508051820.81290.qmail@web10806.mail.yahoo.com> Message-ID: <200205080544.HAA07677@merlin.gams.co.at> Use the default entities. "&" -> & "<" -> < """ -> &quat; and ">" -> > From joe@manyfish.co.uk Wed May 8 03:27:02 2002 From: joe@manyfish.co.uk (Joe Orton) Date: Wed May 8 02:27:02 2002 Subject: [Expat-discuss] [PATCH] support $AUTOCONF/$AUTOHEADER Message-ID: <20020508102403.A23167@light.plus.com> This patch allows specifying an alternative autoconf/autoheader program name, e.g. autoconf-2.53, for when autoconf is configured using --program-name=-2.53. And clean up the autom4te-2.53.cache directory created by such a configuration. (this is especially useful when expat is bundled into other source trees which require a specific version of autoconf to be used, but that version is not 'autoconf' in $PATH) --- buildconf.sh 7 Dec 2001 10:19:30 -0000 1.5 +++ buildconf.sh 8 May 2002 09:24:33 -0000 @@ -35,14 +35,14 @@ # Generate the autoconf header template (config.h.in) and ./configure # echo "Creating config.h.in ..." -autoheader +${AUTOHEADER:-autoheader} echo "Creating configure ..." ### do some work to toss config.cache? -autoconf +${AUTOCONF:-autoconf} # toss this; it gets created by autoconf on some systems -rm -rf autom4te.cache +rm -rf autom4te*.cache # exit with the right value, so any calling script can continue exit 0 From Jean-Francois.Doyon@CCRS.NRCan.gc.ca Thu May 9 14:38:02 2002 From: Jean-Francois.Doyon@CCRS.NRCan.gc.ca (Jean-Francois.Doyon@CCRS.NRCan.gc.ca) Date: Thu May 9 13:38:02 2002 Subject: [Expat-discuss] CDATA Line Length limit ? Message-ID: <7CDD7B94357FD5119E800002A537C46E2300B5@s5-ccr-r1.ccrs.nrcan.gc.ca> Hello, Is there a limit to the length of a line in XML CDATA ? I've got some = XML being returned where the data is one HUGE (hundreds, possibly thousands = of characters) line ... And it looks like the parser is dying or returning = an error ... It's hard for tme to track down because Expat is being used through = Python through an application, but from the various tests I've done, looks = like there is a problem there. Is there such a limit ? What is it ? Can I change it ? If so where ? Also, would there be any relation with the fact that the parser calls = the char_data function many times for the contents of an element ? The fact = that it cuts them up in chunks ? Maybe it does so only so many times ? Any insight on how this works would be very helpfull, as this data that = is causing me problems will be growing even bigger in the future. Thanks in advance for the help! Cheers, Jean-Fran=E7ois Doyon Internet Service Development and Systems Support GeoAccess Division Canadian Center for Remote Sensing Natural Resources Canada http://atlas.gc.ca Phone: (613) 992-4902 Fax: (613) 947-2410 From karl@waclawek.net Thu May 9 14:42:02 2002 From: karl@waclawek.net (Karl Waclawek) Date: Thu May 9 13:42:02 2002 Subject: [Expat-discuss] CDATA Line Length limit ? References: <7CDD7B94357FD5119E800002A537C46E2300B5@s5-ccr-r1.ccrs.nrcan.gc.ca> Message-ID: <024601c1f799$ede4db20$9e539696@citkwaclaww2k> Can you e-mail me the file that causes Expat to die? Karl ----- Original Message ----- From: To: Sent: Thursday, May 09, 2002 4:37 PM Subject: [Expat-discuss] CDATA Line Length limit ? Hello, Is there a limit to the length of a line in XML CDATA ? I've got some XML being returned where the data is one HUGE (hundreds, possibly thousands of characters) line ... And it looks like the parser is dying or returning an error ... It's hard for tme to track down because Expat is being used through Python through an application, but from the various tests I've done, looks like there is a problem there. Is there such a limit ? What is it ? Can I change it ? If so where ? Also, would there be any relation with the fact that the parser calls the char_data function many times for the contents of an element ? The fact that it cuts them up in chunks ? Maybe it does so only so many times ? Any insight on how this works would be very helpfull, as this data that is causing me problems will be growing even bigger in the future. Thanks in advance for the help! Cheers, Jean-François Doyon Internet Service Development and Systems Support GeoAccess Division Canadian Center for Remote Sensing Natural Resources Canada http://atlas.gc.ca Phone: (613) 992-4902 Fax: (613) 947-2410 _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net _______________________________________________ Expat-discuss mailing list Expat-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/expat-discuss From gstein@lyra.org Thu May 9 18:12:05 2002 From: gstein@lyra.org (Greg Stein) Date: Thu May 9 17:12:05 2002 Subject: [Expat-discuss] [PATCH] support $AUTOCONF/$AUTOHEADER In-Reply-To: <20020508102403.A23167@light.plus.com>; from joe@manyfish.co.uk on Wed, May 08, 2002 at 10:24:03AM +0100 References: <20020508102403.A23167@light.plus.com> Message-ID: <20020509171327.K29531@lyra.org> Applied. Thanks! On Wed, May 08, 2002 at 10:24:03AM +0100, Joe Orton wrote: > This patch allows specifying an alternative autoconf/autoheader program > name, e.g. autoconf-2.53, for when autoconf is configured using > --program-name=-2.53. And clean up the autom4te-2.53.cache directory > created by such a configuration. > > (this is especially useful when expat is bundled into other source trees > which require a specific version of autoconf to be used, but that > version is not 'autoconf' in $PATH) > > --- buildconf.sh 7 Dec 2001 10:19:30 -0000 1.5 > +++ buildconf.sh 8 May 2002 09:24:33 -0000 > @@ -35,14 +35,14 @@ > # Generate the autoconf header template (config.h.in) and ./configure > # > echo "Creating config.h.in ..." > -autoheader > +${AUTOHEADER:-autoheader} > > echo "Creating configure ..." > ### do some work to toss config.cache? > -autoconf > +${AUTOCONF:-autoconf} > > # toss this; it gets created by autoconf on some systems > -rm -rf autom4te.cache > +rm -rf autom4te*.cache > > # exit with the right value, so any calling script can continue > exit 0 > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net > _______________________________________________ > Expat-discuss mailing list > Expat-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/expat-discuss -- Greg Stein, http://www.lyra.org/ From kraaer@lycos.com Thu May 16 01:06:03 2002 From: kraaer@lycos.com (John Cooper) Date: Thu May 16 00:06:03 2002 Subject: [Expat-discuss] how to get expat.dll? Message-ID: hi this is a very trivial question but i am new to this. how can i get the expat.dll to get the parser working? thanks! ________________________________________________________ Outgrown your current e-mail service? Get a 25MB Inbox, POP3 Access, No Ads and No Taglines with LYCOS MAIL PLUS. http://login.mail.lycos.com/brandPage.shtml?pageId=plus From gp@familiehaase.de Sun May 19 13:21:05 2002 From: gp@familiehaase.de (Gerrit P. Haase) Date: Sun May 19 12:21:05 2002 Subject: [Expat-discuss] Latest CVS expat sources on Cygwin Message-ID: <67899145693.20020519212023@familiehaase.de> Hallo expat-bugs, building expat (from a checkout today) works without problems. Only doing make install doesn't work if building oputside of the sourcedir which is a requirement to be 'modern';) These hardcoded targets in Makefile.in doesn't allow doing a 'make install' outside the sourcedir: install: xmlwf/xmlwf lib/$(LIBRARY) lib/$(APIHEADER) $(mkinstalldirs) $(bindir) $(libdir) $(includedir) $(LIBTOOL) --mode=install $(INSTALL_PROGRAM) xmlwf/xmlwf $(bindir)/xmlwf $(LIBTOOL) --mode=install $(INSTALL) lib/$(LIBRARY) $(libdir)/$(LIBRARY) $(INSTALL_DATA) lib/$(APIHEADER) $(includedir) $(INSTALL_DATA) doc/xmlwf.1 $(prefix)/man/man1 And also it is not possible to install into a special directory Should look more like this: install: xmlwf/xmlwf lib/$(LIBRARY) $(srcdir)/lib/$(APIHEADER) $(mkinstalldirs) $(DESTDIR)$(bindir) $(DESTDIR)$(libdir) \ $(DESTDIR)$(includedir) $(DESTDIR)$(mandir) $(LIBTOOL) --mode=install $(INSTALL_PROGRAM) xmlwf/xmlwf $(DESTDIR)$(bindir)/xmlwf $(LIBTOOL) --mode=install $(INSTALL) lib/$(LIBRARY) $(DESTDIR)$(libdir)/$(LIBRARY) $(INSTALL_DATA) $(srcdir)/lib/$(APIHEADER) $(DESTDIR)$(includedir) $(INSTALL_DATA) $(srcdir)/doc/xmlwf.1 $(DESTDIR)$(mandir)/man/man1 You're already using autoconf and libtool, why don't you use automake too? That would handle all that stuff. Gerrit -- =^..^= -- From gp@familiehaase.de Sun May 19 13:33:02 2002 From: gp@familiehaase.de (Gerrit P. Haase) Date: Sun May 19 12:33:02 2002 Subject: [Expat-discuss] Latest CVS expat sources on Cygwin In-Reply-To: <67899145693.20020519212023@familiehaase.de> References: <67899145693.20020519212023@familiehaase.de> Message-ID: <77899858317.20020519213216@familiehaase.de> > building expat (from a checkout today) works without problems. > Doing make install doesn't work if building outside of the > sourcedir which is a requirement to be 'modern';) > These hardcoded targets in Makefile.in doesn't allow doing a > 'make install' outside the sourcedir: > install: xmlwf/xmlwf lib/$(LIBRARY) lib/$(APIHEADER) > $(mkinstalldirs) $(bindir) $(libdir) $(includedir) > $(LIBTOOL) --mode=install $(INSTALL_PROGRAM) xmlwf/xmlwf $(bindir)/xmlwf > $(LIBTOOL) --mode=install $(INSTALL) lib/$(LIBRARY) $(libdir)/$(LIBRARY) > $(INSTALL_DATA) lib/$(APIHEADER) $(includedir) > $(INSTALL_DATA) doc/xmlwf.1 $(prefix)/man/man1 > And also it is not possible to install into a special directory > Should look more like this: > install: xmlwf/xmlwf lib/$(LIBRARY) $(srcdir)/lib/$(APIHEADER) > $(mkinstalldirs) $(DESTDIR)$(bindir) $(DESTDIR)$(libdir) \ > $(DESTDIR)$(includedir) $(DESTDIR)$(mandir) > $(LIBTOOL) --mode=install $(INSTALL_PROGRAM) xmlwf/xmlwf $(DESTDIR)$(bindir)/xmlwf > $(LIBTOOL) --mode=install $(INSTALL) lib/$(LIBRARY) $(DESTDIR)$(libdir)/$(LIBRARY) > $(INSTALL_DATA) $(srcdir)/lib/$(APIHEADER) $(DESTDIR)$(includedir) > $(INSTALL_DATA) $(srcdir)/doc/xmlwf.1 $(DESTDIR)$(mandir)/man/man1 Naah, this is completely wrong, ok: define in the Makefile: bindir = ${exec_prefix}/bin libdir = ${prefix}/lib includedir = ${prefix}/include mandir = ${prefix}/man/man1 and then the last line of install target: $(INSTALL_DATA) $(srcdir)/doc/xmlwf.1 $(mandir) The $(DESTDIR) isn't needed then if I use: make install prefix=/blah/usr exec_prefix=/blah/user > You're already using autoconf and libtool, why don't you use automake > too? That would handle all that stuff. > Gerrit -- =^..^= -- From gstein@lyra.org Mon May 20 05:01:02 2002 From: gstein@lyra.org (Greg Stein) Date: Mon May 20 04:01:02 2002 Subject: [Expat-discuss] Latest CVS expat sources on Cygwin In-Reply-To: <67899145693.20020519212023@familiehaase.de>; from gp@familiehaase.de on Sun, May 19, 2002 at 09:20:23PM +0200 References: <67899145693.20020519212023@familiehaase.de> Message-ID: <20020520040343.F15081@lyra.org> On Sun, May 19, 2002 at 09:20:23PM +0200, Gerrit P. Haase wrote: > Hallo expat-bugs, > > building expat (from a checkout today) works without problems. > Only doing make install doesn't work if building oputside of the > sourcedir which is a requirement to be 'modern';) Ah. Yes, it should be able to do that. I didn't realize that it was (recently) broken. >... > And also it is not possible to install into a special directory > Should look more like this: > > install: xmlwf/xmlwf lib/$(LIBRARY) $(srcdir)/lib/$(APIHEADER) The srcdir should not be required on the dependency list. When doing a VPATH build, 'make' should automatically look in both the source and the build areas for source/dependency information. > $(mkinstalldirs) $(DESTDIR)$(bindir) $(DESTDIR)$(libdir) \ > $(DESTDIR)$(includedir) $(DESTDIR)$(mandir) DESTDIR is nice, but I like your prefix/exec_prefix stuff better. I'll take a look at a good option for that. I might put DESTDIR in there, too, since that seems to be relatively common (I've seen people ask for it in Subversion). >... > You're already using autoconf and libtool, why don't you use automake > too? That would handle all that stuff. automake is awful. horrible. evil. unspeakable. I can't even begin to count the ways. And it is plain and simple overbearing and overkill for the Expat project. I spent a ton of time ripping out some remnants of automake in the Expat build system. We aren't going to put it back in. Okay... maybe that was a bit harsh :-), but really... automake is just unbearably awful. Cheers -g -- Greg Stein, http://www.lyra.org/ From gp@familiehaase.de Mon May 20 14:06:06 2002 From: gp@familiehaase.de (Gerrit P. Haase) Date: Mon May 20 13:06:06 2002 Subject: [Expat-discuss] Latest CVS expat sources on Cygwin In-Reply-To: <20020520040343.F15081@lyra.org> References: <67899145693.20020519212023@familiehaase.de> <20020520040343.F15081@lyra.org> Message-ID: <76988278739.20020520220556@familiehaase.de> Hallo Greg, Am Montag, 20. Mai 2002 um 13:03 schriebst du: >> You're already using autoconf and libtool, why don't you use automake >> too? That would handle all that stuff. > automake is awful. horrible. evil. unspeakable. > I can't even begin to count the ways. And it is plain and simple overbearing > and overkill for the Expat project. I spent a ton of time ripping out some > remnants of automake in the Expat build system. We aren't going to put it > back in. > Okay... maybe that was a bit harsh :-), but really... automake is just > unbearably awful. Well, ok. As long as it works without;) Gerrit -- =^..^= From al-expat@none.at Wed May 29 01:30:02 2002 From: al-expat@none.at (Alexander Lazic) Date: Wed May 29 00:30:02 2002 Subject: [Expat-discuss] Problem with utf-8 on windows(98/2k) Message-ID: <20020529072919.GA32074@none.at> Hi, i have write some SW on Cygwin/Win98 and use it on W2k. When i get an xml with: . . . . bernahme aus GSG . . . Expat stop parsing and write: 'unclosed token at line xxx' which is clear because he don't see the closed token. how can i fix this? Thanx for your help. al ;-) From al-expat@none.at Wed May 29 02:09:03 2002 From: al-expat@none.at (Alexander Lazic) Date: Wed May 29 01:09:03 2002 Subject: [Expat-discuss] Expat from CVS Message-ID: <20020529080820.GA32488@none.at> Hi, today i get the cvs-Version from expat ;-) After call of 'autoheader && autoconf && ./configure' on cygwin i get the following error: configure.in:56: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.in:57: error: possibly undefined macro: AC_PROG_LIBTOOL ^^^^^^^^? $ autoheader --version autoheader (GNU Autoconf) 2.53a Written by Roland McGrath and Akim Demaille. autoconf (GNU Autoconf) 2.53a Written by David J. MacKenzie and Akim Demaille. Is this the right way to make 'libexpat*.dll' from cvs? Where can i get this macros? Thanx for help al ;-) From al-expat@none.at Wed May 29 06:19:01 2002 From: al-expat@none.at (Alexander Lazic) Date: Wed May 29 05:19:01 2002 Subject: [Expat-discuss] Question about 'preparing for 1.95.3' Message-ID: <20020529121754.GA4085@none.at> Hi, Fred when does you think 1.95.3 will release ;-) al ;-) From al-expat@none.at Wed May 29 10:53:04 2002 From: al-expat@none.at (Alexander Lazic) Date: Wed May 29 09:53:04 2002 Subject: [Expat-discuss] Please help me on cygwin. Message-ID: <20020529165215.GA13559@none.at> This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. ---------------------- multipart/mixed attachment Hi, today i get the cvs version (2002-05-29 17:08). I have make a: sh -x ./buildconf.sh >buildconf_out 2>&1 ./configure >configure_out 2>&1 make >make_out 2>&1 but i can't get a libexpat.dll nor a libexpat.la. $ gcc --version 2.95.3-5 $ autoheader --version autoheader (GNU Autoconf) 2.53a Written by Roland McGrath and Akim Demaille. $ autoconf --version autoconf (GNU Autoconf) 2.53a Written by David J. MacKenzie and Akim Demaille. $ /usr/bin/libtoolize --version libtoolize (GNU libtool) 1.4.2 $ ./libtool --version ltmain.sh (GNU libtool) 1.4.2 (1.922.2.54 2001/09/11 03:33:37) Please can anybody help me? Thanx if you help ;-) al ;-) ---------------------- multipart/mixed attachment + echo Copying libtool helper files ... Copying libtool helper files ... + conftools/PrintPath glibtoolize libtoolize + libtoolize=/usr/bin/libtoolize + [ x/usr/bin/libtoolize = x ] + cd conftools/ + rm -f ltmain.sh ltconfig + /usr/bin/libtoolize --force --copy --automake + dirname /usr/bin/libtoolize + ltpath=/usr/bin + cd /usr/bin/../share/aclocal + pwd + ltfile=/usr/share/aclocal/libtool.m4 + cp /usr/share/aclocal/libtool.m4 conftools/libtool.m4 + rm -f aclocal.m4 + echo Creating expat_config.h.in ... Creating expat_config.h.in ... + autoheader autoheader: `expat_config.h.in' is created + echo Creating configure ... Creating configure ... + autoconf + rm -rf autom4te.cache + exit 0 ---------------------- multipart/mixed attachment /bin/bash ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -Ilib -I. -o lib/xmlparse.lo -c lib/xmlparse.c /bin/bash ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -Ilib -I. -o lib/xmltok.lo -c lib/xmltok.c /bin/bash ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -Ilib -I. -o lib/xmlrole.lo -c lib/xmlrole.c /bin/bash ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -Ilib -I. -no-undefined -version-info 1:0:1 -rpath /usr/local/lib -o lib/libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo /usr/lib/libcygwin.a(libcmain.o)(.text+0x6a): undefined reference to `WinMain@16' collect2: ld returned 1 exit status make: *** [lib/libexpat.la] Error 1 ---------------------- multipart/mixed attachment checking build system type... i586-pc-cygwin checking host system type... i586-pc-cygwin checking for gcc... gcc checking for C compiler default output... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for ld used by GCC... /usr/i686-pc-cygwin/bin/ld.exe checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic file format pei*-i386(.*architecture: i386)? checking command to parse /usr/bin/nm -B output... ok checking how to run the C preprocessor... 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... no 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 gcc option to produce PIC... -DDLL_EXPORT checking if gcc PIC flag -DDLL_EXPORT works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... Win32 ld.exe 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) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking for a BSD-compatible install... /usr/bin/install -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... no 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... no checking for memmove... yes checking for bcopy... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h ---------------------- multipart/mixed attachment-- From gp@familiehaase.de Thu May 30 01:02:02 2002 From: gp@familiehaase.de (Gerrit P. Haase) Date: Thu May 30 00:02:02 2002 Subject: [Expat-discuss] Please help me on cygwin. In-Reply-To: <20020529165215.GA13559@none.at> References: <20020529165215.GA13559@none.at> Message-ID: <1301804917424.20020530090146@familiehaase.de> Hallo Alexander, > today i get the cvs version (2002-05-29 17:08). > I have make a: The last time I tried to build it it works fine. I'm using the devel packages of libtool and autoconf. I'll do a new checkout today and see what was changed. Gerrit -- =^..^= From al-expat@none.at Thu May 30 01:05:05 2002 From: al-expat@none.at (Alexander Lazic) Date: Thu May 30 00:05:05 2002 Subject: [Expat-discuss] Please help me on cygwin. In-Reply-To: <1301804917424.20020530090146@familiehaase.de> References: <20020529165215.GA13559@none.at> <1301804917424.20020530090146@familiehaase.de> Message-ID: <20020530070434.GA32571@none.at> On Don 30.05.2002 09:01, Gerrit P. Haase wrote: >Hallo Alexander, Hi, >> today i get the cvs version (2002-05-29 17:08). >> I have make a: > >The last time I tried to build it it works fine. >I'm using the devel packages of libtool and autoconf. Hm i will try with devel ;-) >I'll do a new checkout today and see what was changed. Thanx. al ;-) From al-expat@none.at Thu May 30 04:09:07 2002 From: al-expat@none.at (Alexander Lazic) Date: Thu May 30 03:09:07 2002 Subject: [Expat-discuss] Please help me on cygwin. In-Reply-To: <1301804917424.20020530090146@familiehaase.de> References: <20020529165215.GA13559@none.at> <1301804917424.20020530090146@familiehaase.de> <20020530070434.GA32571@none.at> Message-ID: <20020530100843.GA3235@none.at> This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. ---------------------- multipart/mixed attachment On Don 30.05.2002 09:01, Gerrit P. Haase wrote: >Hallo Alexander, Hi, today i get the cvs version (2002-05-30 10:45). >The last time I tried to build it it works fine. >I'm using the devel packages of libtool and autoconf. I have now installed the devel package and get the following error: /bin/bash ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -Ilib -I. -o lib/xmlparse.lo -c lib/xmlparse.c ./libtool: s%^.*/%%: No such file or directory ./libtool: -e: command not found al@WINDOWS /usr/src/expat-cvs/expat-2002-05-30_10-45 $ ./libtool --version ./libtool: s%^.*/%%: No such file or directory ltmain.sh (GNU libtool) 1.4e (1.1103 2002/05/02 14:22:51) $ autoheader --version autoheader (GNU Autoconf) 2.53a Written by Roland McGrath and Akim Demaille. $ /usr/bin/libtoolize --version libtoolize (GNU libtool) 1.4e $ autoconf --version autoconf (GNU Autoconf) 2.53a Written by David J. MacKenzie and Akim Demaille. The path for auto* will be expanded to: + exportPATH=/usr/autotool/devel/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/W INDOWS:/cygdrive/c/WINDOWS/COMMAND + export M4PATH=/usr/autotool/devel/share/autoconf: Thanx for your help al ;-) ---------------------- multipart/mixed attachment + echo Copying libtool helper files ... Copying libtool helper files ... + conftools/PrintPath glibtoolize libtoolize + libtoolize=/usr/bin/libtoolize + [ x/usr/bin/libtoolize = x ] + cd conftools/ + rm -f ltmain.sh ltconfig + /usr/bin/libtoolize --force --copy --automake + dirname /usr/bin/libtoolize + ltpath=/usr/bin + cd /usr/bin/../share/aclocal + pwd + ltfile=/usr/share/aclocal/libtool.m4 + cp /usr/share/aclocal/libtool.m4 conftools/libtool.m4 + rm -f aclocal.m4 + echo Creating expat_config.h.in ... Creating expat_config.h.in ... + autoheader autoheader: `expat_config.h.in' is created + echo Creating configure ... Creating configure ... + autoconf + rm -rf autom4te.cache + exit 0 ---------------------- multipart/mixed attachment checking build system type... i586-pc-cygwin checking host system type... i586-pc-cygwin checking for gcc... gcc checking for C compiler default output... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for ld used by GCC... /usr/i686-pc-cygwin/bin/ld.exe checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic file format pei*-i386(.*architecture: i386)? checking command to parse /usr/bin/nm -B output... ok checking how to run the C preprocessor... 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... no 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 gcc option to produce PIC... -DDLL_EXPORT checking if gcc PIC flag -DDLL_EXPORT works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... Win32 ld.exe 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) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking for a BSD-compatible install... /usr/bin/install -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... no 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... no checking for memmove... yes checking for bcopy... yes configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h ---------------------- multipart/mixed attachment /bin/bash ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -Ilib -I. -o lib/xmlparse.lo -c lib/xmlparse.c ./libtool: s%^.*/%%: No such file or directory ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found ./libtool: -e: command not found : compile: cannot determine name of library object from `' make: *** [lib/xmlparse.lo] Error 1 ---------------------- multipart/mixed attachment-- From ritesh_garodia@hp.com Thu May 30 07:20:07 2002 From: ritesh_garodia@hp.com (Ritesh Garodia) Date: Thu May 30 06:20:07 2002 Subject: [Expat-discuss] Compile error using cc Message-ID: <007301c207dc$9a614260$2478cc0f@GARODIA> This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment hi, I am trying to compile on HP UX 11i, it gives following error for make Entering directory `/home/ritesh/expat-1.95.2/lib' /bin/sh ../libtool --mode=3Dcompile cc -DHAVE_CONFIG_H = -DPACKAGE=3D'"expat"' -DVERSION=3D'"expat_1.95.2"' -I. -I. -I.. -c = xmlparse.c cc -DHAVE_CONFIG_H -DPACKAGE=3D\"expat\" -DVERSION=3D\"expat_1.95.2\" = -I. -I. -I.. -c xmlparse.c -o xmlparse.o (Bundled) cc: "expat.h", line 80: error 1000: Unexpected symbol: = "XML_Char". (Bundled) cc: "expat.h", line 81: error 1000: Unexpected symbol: "*". (Bundled) cc: error 2017: Cannot recover from earlier errors, = terminating. Any help is highly appreciated. Thanx Ritesh Garodia ---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.libexpat.org/pipermail-21/expat-discuss/attachments/20020530/5b111122/attachment.html ---------------------- multipart/alternative attachment-- From stlouis@crd.ge.com Thu May 30 10:18:04 2002 From: stlouis@crd.ge.com (St. Louis, Thomas (Research)) Date: Thu May 30 09:18:04 2002 Subject: [Expat-discuss] Looking for sample code using ExternalEntityRefHandler Message-ID: Hi, I'm using the expat parser for a Pocket PC app developed using MS emBedded C++ and the std XML_ParserCreate doesn't work very well for the following tag: Anything containing encoded data such as &<96D>Accepted I beleive I need to set entity parsing to XML_PARAM_ENTITY_PARSING_NEVER . The function is not available to me which probably means my compilation of expat is missing something. It's not clear to me what should be in the ExternalEntityRefHandler callback function. Any help is appreciated. Thanks Tom g GE Global Research Center _____________________________________________________________________________________________________ __________________________________________________________ Tom St.Louis Computer Scientist Advanced Computing Technologies One Research Circle, K1-5B32 Niskayuna, NY 12309 8*833-4900 stlouis@crd.ge.com From fdrake@acm.org Thu May 30 15:12:02 2002 From: fdrake@acm.org (Fred L. Drake, Jr.) Date: Thu May 30 14:12:02 2002 Subject: [Expat-discuss] Question about 'preparing for 1.95.3' In-Reply-To: <20020529121754.GA4085@none.at> References: <20020529121754.GA4085@none.at> Message-ID: <15606.38262.816862.583540@grendel.zope.com> Alexander Lazic writes: > Fred when does you think 1.95.3 will release ;-) We've got a couple of build/packaging things to take care of, then it's ready. We got the last real bug fix we're planning for this release checked in today, thanks to Karl. -Fred -- Fred L. Drake, Jr. PythonLabs at Zope Corporation From al-expat@none.at Fri May 31 02:20:01 2002 From: al-expat@none.at (Alexander Lazic) Date: Fri May 31 01:20:01 2002 Subject: [Expat-discuss] Parse error on "umlaut U" Message-ID: <20020531081855.GA3746@none.at> Hi, if i have a "umlaut U" in the xml-doc i get a parsing error. The parser doesen't see the end-Tag ;-/ but only on "umlaut U". Please can anybody help me. al ;-) From al-expat@none.at Fri May 31 02:36:02 2002 From: al-expat@none.at (Alexander Lazic) Date: Fri May 31 01:36:02 2002 Subject: Addendum: [Expat-discuss] Parse error on "umlaut U" In-Reply-To: <20020531081855.GA3746@none.at> References: <20020531081855.GA3746@none.at> Message-ID: <20020531083455.GA4062@none.at> Hi, >if i have a "umlaut U" in the xml-doc i get a parsing error. > >The parser doesen't see the end-Tag ;-/ but only on "umlaut U". > >Please can anybody help me. I have forget to tell which version from expat: version from cvs 2002-05-30 at 10:40 on Cygwin. al ;-) From karl@waclawek.net Fri May 31 04:56:02 2002 From: karl@waclawek.net (Karl Waclawek) Date: Fri May 31 03:56:02 2002 Subject: Addendum: [Expat-discuss] Parse error on "umlaut U" References: <20020531081855.GA3746@none.at> <20020531083455.GA4062@none.at> Message-ID: <002101c20894$353f5440$0207a8c0@karl> > Hi, > > >if i have a "umlaut U" in the xml-doc i get a parsing error. > > > >The parser doesen't see the end-Tag ;-/ but only on "umlaut U". > > > >Please can anybody help me. > > I have forget to tell which version from expat: > > version from cvs 2002-05-30 at 10:40 on Cygwin. > Post a small document that shows the problem. Karl From al-expat@none.at Fri May 31 05:05:02 2002 From: al-expat@none.at (Alexander Lazic) Date: Fri May 31 04:05:02 2002 Subject: Addendum: [Expat-discuss] Parse error on "umlaut U" In-Reply-To: <002101c20894$353f5440$0207a8c0@karl> References: <20020531081855.GA3746@none.at> <20020531083455.GA4062@none.at> <002101c20894$353f5440$0207a8c0@karl> Message-ID: <20020531110413.GB4062@none.at> On Fre 31.05.2002 07:13, Karl Waclawek wrote: >> Hi, Hi, and thanx for your response ;-)) >Post a small document that shows the problem. it is not so small and therefore you can find it at: http://members.bursik.net/~al/out.xml al ;-) From gp@familiehaase.de Fri May 31 05:28:05 2002 From: gp@familiehaase.de (Gerrit P. Haase) Date: Fri May 31 04:28:05 2002 Subject: Addendum: [Expat-discuss] Parse error on "umlaut U" In-Reply-To: <20020531110413.GB4062@none.at> References: <20020531081855.GA3746@none.at> <20020531083455.GA4062@none.at> <002101c20894$353f5440$0207a8c0@karl> <20020531110413.GB4062@none.at> Message-ID: <3247551926.20020531132749@familiehaase.de> ---------------------- multipart/mixed attachment Hallo Alexander, >>Post a small document that shows the problem. > it is not so small and therefore you can find it at: > http://members.bursik.net/~al/out.xml Length: 2,798 [text/xml] this really small...why do you think it is not so small? I fetched it and attached it now;) Gerrit -- =^..^= ---------------------- multipart/mixed attachment A non-text attachment was scrubbed... Name: out.xml Type: application/xml Size: 3782 bytes Desc: not available Url : http://mail.libexpat.org/pipermail-21/expat-discuss/attachments/20020531/f6bcb716/out.rdf ---------------------- multipart/mixed attachment-- From al-generic@none.at Fri May 31 05:38:01 2002 From: al-generic@none.at (Alexander Lazic) Date: Fri May 31 04:38:01 2002 Subject: Addendum: [Expat-discuss] Parse error on "umlaut U" In-Reply-To: <3247551926.20020531132749@familiehaase.de> References: <20020531081855.GA3746@none.at> <20020531083455.GA4062@none.at> <002101c20894$353f5440$0207a8c0@karl> <20020531110413.GB4062@none.at> <3247551926.20020531132749@familiehaase.de> Message-ID: <20020531113659.GA7348@none.at> On Fre 31.05.2002 13:27, Gerrit P. Haase wrote: >Hallo Alexander, Hi, >Length: 2,798 [text/xml] > >this really small...why do you think it is not so small? > >I fetched it and attached it now;) Thanx. Hm we have some different definiton of 'small' ;-)) al ;-) From karl@waclawek.net Fri May 31 07:04:07 2002 From: karl@waclawek.net (Karl Waclawek) Date: Fri May 31 06:04:07 2002 Subject: Addendum: [Expat-discuss] Parse error on "umlaut U" References: <20020531081855.GA3746@none.at> <20020531083455.GA4062@none.at> <002101c20894$353f5440$0207a8c0@karl> <20020531110413.GB4062@none.at> Message-ID: <001f01c208a3$8b64b680$9e539696@citkwaclaww2k> > On Fre 31.05.2002 07:13, Karl Waclawek wrote: > > >> Hi, > > Hi, > > and thanx for your response ;-)) > > >Post a small document that shows the problem. > > it is not so small and therefore you can find it at: > > http://members.bursik.net/~al/out.xml > > al ;-) > I have no problem with your file using the current CVS. However, I checked in a patch for UTF-8 detection yesterday, possibly after you checked out your build. Check it out and try again (the patch is limited to the file xmltok.c). If that does not help, then maybe we have a Cygwin problem. Karl From gp@familiehaase.de Fri May 31 07:26:03 2002 From: gp@familiehaase.de (Gerrit P. Haase) Date: Fri May 31 06:26:03 2002 Subject: [Expat-discuss] Parse error on "umlaut U" In-Reply-To: <20020531081855.GA3746@none.at> References: <20020531081855.GA3746@none.at> Message-ID: <10754623854.20020531152541@familiehaase.de> Hallo Alexander, Am Freitag, 31. Mai 2002 um 10:18 schriebst du: > Hi, > if i have a "umlaut U" in the xml-doc i get a parsing error. > The parser doesen't see the end-Tag ;-/ but only on "umlaut U". $ /usr/bin/xmlwf out.xml $ xmlwf -eUTF-8 out.xml I get no reply from these commands. That means no error. Gerrit -- =^..^= From al-expat@none.at Fri May 31 14:02:05 2002 From: al-expat@none.at (Alexander Lazic) Date: Fri May 31 13:02:05 2002 Subject: [Expat-discuss] Parse error on "umlaut U" In-Reply-To: <10754623854.20020531152541@familiehaase.de> References: <20020531081855.GA3746@none.at> <10754623854.20020531152541@familiehaase.de> Message-ID: <20020531200141.GA17667@none.at> On Fre 31.05.2002 15:25, Gerrit P. Haase wrote: >Hallo Alexander, Hi, >I get no reply from these commands. That means no error. Hm i also, but in my app it doesn't work!? how can i 'turn on' debug in (lib)?expat? ;-)) al ;-) From fdrake@acm.org Fri May 31 20:41:03 2002 From: fdrake@acm.org (Fred L. Drake, Jr.) Date: Fri May 31 19:41:03 2002 Subject: [Expat-discuss] Expat 1.95.3 coming up Message-ID: <15608.13351.386784.679762@grendel.zope.com> A recurring complaint about recent Expat versions from users of the XML::Parser package has been that the name of the Expat DLL clashes with the name of the DLL containing the XML::Parser::Expat Perl module. In the upcoming release of Expat, 1.95.3, we're renaming the DLL to libexpat.dll (from expat.dll), so this should no longer be a problem. I've placed a pre-release Windows installer for Expat 1.95.3 at: http://expat.sourceforge.net/expat_win32bin_1_95_3_pre.exe I'd really like to hear back from anyone who can test it with the Perl bindings. Please let me know how it goes; if you have any problems using it, file a bug report on SourceForge: http://sourceforge.net/tracker/?atid=110127&group_id=10127&func=browse If all goes well, please let us know as well by sending a note to the expat-discuss list: http://sourceforge.net/mail/?group_id=10127 Thanks! -Fred -- Fred L. Drake, Jr. PythonLabs at Zope Corporation From fdrake@acm.org Fri May 31 20:48:02 2002 From: fdrake@acm.org (Fred L. Drake, Jr.) Date: Fri May 31 19:48:02 2002 Subject: [Expat-discuss] Expat 1.95.3 coming up Message-ID: <15608.13745.20330.564866@grendel.zope.com> A recurring complaint about recent Expat versions from users of the XML::Parser package has been that the name of the Expat DLL clashes with the name of the DLL containing the XML::Parser::Expat Perl module. In the upcoming release of Expat, 1.95.3, we're renaming the DLL to libexpat.dll (from expat.dll), so this should no longer be a problem. I've placed a pre-release Windows installer for Expat 1.95.3 at: http://expat.sourceforge.net/expat_win32bin_1_95_3_pre.exe I'd really like to hear back from anyone who can test it with the Perl bindings. Please let me know how it goes; if you have any problems using it, file a bug report on SourceForge: http://sourceforge.net/tracker/?atid=110127&group_id=10127&func=browse If all goes well, please let us know as well by sending a note to the expat-discuss list: http://sourceforge.net/mail/?group_id=10127 Thanks! -Fred -- Fred L. Drake, Jr. PythonLabs at Zope Corporation