From DZhao1@prius.jnj.com Tue Dec 5 21:49:38 2000 From: DZhao1@prius.jnj.com (Zhao, David [PRI]) Date: Tue, 5 Dec 2000 16:49:38 -0500 Subject: [Expat-discuss] expat installation problem Message-ID: <8FB723D60C5AD411969A00508B69860325E1C2@rarusljexs7.prius.jnj.com> This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ---------------------- multipart/alternative attachment I am trying to install expat library under my own lib directory, I did: ./configure --prefix=/home/iblast/my_lib make make install and I got error message: /bin/sh ../libtool --mode=compile cc -DHAVE_CONFIG_H -DPACKAGE=expat -DVERSION=expat_1.95.1 -I. -I.. -g -c xmlparse.c rm -f .libs/xmlparse.lo cc -DHAVE_CONFIG_H "-DPACKAGE=\"expat\"" "-DVERSION=\"expat_1.95.1\"" -I. -I.. -g -Wp,-MD,.deps/xmlparse.pp -c xmlparse.c -DPIC -o .libs/xmlparse.lo cc-1574 cc: ERROR The definition of macro %sq is not valid. cc-1005 cc: ERROR The source file ".deps/xmlparse.pp" is unavailable. 2 catastrophic errors detected in the compilation of ".deps/xmlparse.pp". Compilation terminated. *** Error code 1 (bu21) *** Error code 1 (bu21) Please help, thanks in advance! David > David Zhao > Drug Discovery IM&T > The R.W.Johnson PRI > 3210 Merryfield Row > San Diego, CA 92121 > Tel: (858) 784-3184 > > ---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.libexpat.org/pipermail-21/expat-discuss/attachments/20001205/ede8b1e3/attachment.html ---------------------- multipart/alternative attachment-- From kaiserovi@worldmail.cz Tue Dec 12 20:21:26 2000 From: kaiserovi@worldmail.cz (Kaiserovi) Date: Tue, 12 Dec 2000 21:21:26 +0100 Subject: [Expat-discuss] expat 1.95 on win32 Message-ID: <3A3688C6.C4C68DB5@worldmail.cz> Hello, first of all, thanks for this great version of expat. I'm trying to provide a uniform way to link our product (an XSLT processor called Sablotron) with expat 1.95 when building on win32. We'd like to be able to use the binary distribution of expat as well as the source one. We need to access expat.h and expat.lib in the build, but would like to avoid asking for the full paths to these 2 files. However, we encountered the following problems: - the DLL in the binary distribution (expat_1_95_1.dll) is named differently from the one produced from the sources (expat.dll), - the .lib file is not included among the binaries. Is this on purpose? Also, wouldn't it be better to use the same names and the same directory structure for the binaries (plus expat.h) in the two distributions? BTW, I assume one should use the LIB utility to produce a .lib from the .dll in the binary distribution, but I wasn't able to do so without using the object files. Is there a way? Thank you, Tom Kaiser (Ginger Alliance) From mike.wilson@tradeweb.com Wed Dec 13 16:17:00 2000 From: mike.wilson@tradeweb.com (MIke Wilson) Date: Wed, 13 Dec 2000 11:17:00 -0500 Subject: [Expat-discuss] cygwin building difficulty Message-ID: I'm having a bit of selective "undoubtably newbie-based" trouble building an expat "hello world" app. The expat source & libraries build without event, as does xmlwf. However when setting up a simple makefile (small enough to have dropped in below) and a void cpp source file that just includes expat.h, I receive the following errors... In file included from xpt.cpp:16: d:/code/tp/expat/expat-1.95.1/lib/expat.h:547: parse error before `__attribute__' (and the same for 3 more lines, 686, 701, & 705) Have I botched the includes? TIA, - Mike # # Makefile # CC=g++ EXPAT_DIR=d:/code/tp/expat/expat-1.95.1 EXPAT_LIBDIR=$(EXPAT_DIR)/lib/.libs EXPAT_INCDIR=$(EXPAT_DIR)/lib INCLUDE=$(EXPAT_INCDIR) %.o: %.cpp ; $(CC) -c -I$(INCLUDE) $(CFLAGS) $(CPPFLAGS) $< -o $@ BINOBJS=xpt.o APPS=xptest build: $(BINOBJS) $(APPS) xptest: $(BINOBJS) $(CC) -o xpt.o -L$(EXPAT_LIBDIR) -lexpat From sive@sell.bd.se Wed Dec 13 23:45:34 2000 From: sive@sell.bd.se (Sive Lindmark) Date: Thu, 14 Dec 2000 00:45:34 +0100 Subject: [Expat-discuss] expat on macos x Message-ID: <3A380A1E.5070101@sell.bd.se> Hi all! New on this list. I have tried expat on linux before and now I try to move my project to maxos x. Does anybody know if someone have ported expat to maxos x? (Run in trouble with the configure script.) Greetings from Sweden Sive From ken@bitsko.slc.ut.us Thu Dec 14 16:45:28 2000 From: ken@bitsko.slc.ut.us (Ken MacLeod) Date: 14 Dec 2000 10:45:28 -0600 Subject: [Expat-discuss] expat on macos x In-Reply-To: Sive Lindmark's message of "Thu, 14 Dec 2000 00:45:34 +0100" References: <3A380A1E.5070101@sell.bd.se> Message-ID: Sive Lindmark writes: > I have tried expat on linux before and now I try to move my project > to maxos x. Does anybody know if someone have ported expat to maxos > x? (Run in trouble with the configure script.) This isn't the same, but for reference, expat-1.95.1 configures and compiles clean on MacOS X *Server* 1.0 and 1.2, and I haven't had any problems running it so far. Host system type powerpc-apple-rhapsody5.6 I haven't tried it on MOSX Public Beta yet, waiting for Apple to clean up their act on packaging issues before doing any development there. It's possible that the development environment you've installed isn't installed completely or correctly. Have you been able to compile other packages? What does configure say is wrong? MOSXbeta is a FreeBSD clone if that helps anyone. -- Ken From dev@humph.com Mon Dec 18 02:28:37 2000 From: dev@humph.com (Giuliano Gavazzi) Date: Mon, 18 Dec 2000 02:28:37 +0000 Subject: [Expat-discuss] expat on MacOS Classic and X Message-ID: Hi all, I have just asked Ken to forward a message to the list regarding expat on MacOSX Beta. But since then I have subscribed to the list as it might be something I'll be working on for a project of mine. Well, expat_1.95.1 compiles fine and seems to run fine on X Beta as long as you install autoconf (required by the build process). Just do: autoconf ./configure make make install I tested outline.c and it works fine on a couple of test xml. I then wanted to see if it worked also on MacOS Classic (for the moment just PPC, but of course should also work on Carbon, as there should be no differences in standard C). It compiles with some warnings and it produces a working library, again tested compiling outline.c. This requires a few modifications as there is no Makefile involved (I used CodeWarrior). Also outline.c required a few changes, mainly because I had no time to see how to make stdin to work properly in this particular case. I read the input from a file instead of stdin and the parsing worked as expected. As soon as I have this cleaned up I will submit the projects, but to whom? Thanks for the attention Giuliano -- H U M P H || ||| software development of: Java & C++ Server/Client/Human Interface applications on MacOS - MacOS X http://www.humph.com/ From kmorehead@idiominc.com Wed Dec 27 21:21:46 2000 From: kmorehead@idiominc.com (Kem Morehead) Date: Wed, 27 Dec 2000 16:21:46 -0500 Subject: [Expat-discuss] compiling for Windows NT Message-ID: <43EA80F14C3ED411841D00508BAE017D646A59@WAL-ZULU> Hi, While trying to compile expat-1.95.1 for Windows NT, we encountered the following problems: 1. While expat.dll compiled fine in debug mode, the release configuration gave us many errors. After poking around a bit, we found the problem in the setting for xmltok_impl.c and xmltok_ns.c. These two files were excluded from the build in the debug configuration but not in the release configuration. After excluding them from the release configuration, the compilation was okay. 2. The VERSION definition kept on giving us problems during the build for the release configuration but not in the debug. We think it may be due to the way the double quotes are placed around it. In the end we just placed the definition directly in expat.h and things were okay. Other than that things seemed to work generally very well on win32. thanks for all the good work! kem ------------------------------------------------- Kem Morehead, software engineer Idiom, Inc. [www.idiominc.com] 781.464.6113 kmorehead@idiominc.com