From: Steve B. <Ste...@zv...> - 2004-02-04 11:17:25
|
Hi Rich, TclXML version 3.0 is in beta release at the moment. One implication of its beta status is that not all release engineering has been performed, so the build system may not be entirely robust. I'm planning on getting those issues resolved when the packages are made final. As far as the 'make test' target is concerned I've been doing alot of work on that lately, but mostly since the beta1 release. At the moment I assume that the packages are fully installed before they can be tested - not a good assumption and something that probably needs more work. Finally, the "libxml2, v3.0" vs "libxml, v23.0" issue is tricky. However, I have got it working on my Mac OSX, Linux and Windows systems. I'm working towards a beta2 release soon, so hopefully alot of these problems will have been resolved. Cheers, Steve Ball On 03/02/2004, at 11:27, R. T. Wurth wrote: > I am having quite a bit of trouble building tclxml version 3.0. > > It is not clear to me whether I should use the installer in the top > directory or do the configure/make/install cycle, so I did both > (installer first). I found I needed to run autoconf to generate the > config file. This I found strange because most packages come with a > pre-generated config file. Then I started on the subdirectories, > per the instructions. > > In expat, I had to edit the configure file to bump the version to > 3.0. (Looking at SF CVS, I see it's out of date w/resp. to > configure.in.) > > In libxml2, I had to do the same. In addition, I found the 'test' > step of the Makefile' has a bug. Where it refers to > $TclXML_LIBXML2_LIB_FILE, it should refer to > $TclXML_libxml2_LIB_FILE (note upper vs. lower case libxml2). But > now, I am at my wit's end. When I do try to test the package, it > fails with error message: > couldn't find procedure Tclxml_libxml_Init > I couldn't find a function with that name in the code, but I did > find Tclxml_libxml2_Init. I think the problem is that the library > file is named libTclXML_libxml23.0.sl, which is intended to mean it > is libTclXML_libxml2, version 3.0, however, the Tcl interpreter's > simple parsing rules interpret it as libTclXML_libxml, version 23.0. > Thus, it is missing the terminal 2 when it constructs the name of > the library's Init proc. I don't have any idea how this might be > fixed simply. It strikes me as an architectural issue that might > require changing the package name to not have a terminal digit. I > don't see how anyone could have built this or any prior version and > gotten it to work with this bug, so I have to wonder if there is > something wrong with my configuration causing me to have this problem. > > Would you like SF bug reports on these? Do you prefer all-in one, > one per package (2 total, 1 each for expat, and libxml2), or one per > problem (3 total, splitting the two libxml2 problems into separate > issues)? > > Thanks for nay help you can provide. > -- > Rich Wurth / rw...@at... / Rumson, NJ USA > Steve Ball | XSLT Standard Library | Training & Seminars Zveno Pty Ltd | Web Tcl Complete | XML XSL Schemas http://www.zveno.com/ | TclXML TclDOM | Tcl, Web Development Ste...@zv... +---------------------------+--------------------- Ph. +61 2 6242 4099 | Mobile (0413) 594 462 | Fax +61 2 6242 4099 |