From: Andreas K. <and...@Ac...> - 2002-08-15 22:23:40
|
> ------- Forwarded Message > > From: "Larry W. Virden" <lv...@ca...> > Subject: [Tclxml-users] Report of my attempt to install tcldom 2.2 > Sender: tcl...@li... > To: tcl...@li... > Message-id: <200...@ca...> Here are my experiences after having read the message below. 1. Got head of Tcl 8.3.4 branch 1.a Compiled and installed in playground/sandbox 2. Got head of tclxml/tcldom 2.a Ran autoconf 2.b. Configured with same prefix as tcl, did --enable-xml2 configure did not find xml2 There is nothing in the docs telling us where we can get libxml2. Stop. Nit: make distclean leaves two directories behind, library and src-libxml2 (in the build directory). Can be explained because srcdir contains these two directories too, often builddir = srcdir. I tried a second configure of tcldom, with --disable-xml2. No errors for that. Compilation fails nevertheless because the makefile tried to compile the sources in src-libxml2 despite the fact that I just told it that libxml2 is not available. That is not acceptable. A configure option which does nothing at all. More comments below. > 1. The activestate cvs snapshot does not apparently reflect tcldom 2.2 - > anyone know why? No. At least the changelog in the latest snapshot (Aug 12) looks as if it is a part of tcldom 2.2. > 2. The sf.net tar file didn't include top level configure - > is configure supposed to be done elsewhere? The README isn't clear. IMHO the source distribution has to have a 'configure'. For a checkout from the CVS the situation is more fuzzy. > 3. After I ran autoconf to create the configure, configure > reports this error: > configure: error: cannot run /bin/ksh config/config.sub Not here. > 4. after supplying that file, configure reports this error: > checking build system type... /bin/ksh: config/config.guess: not found > configure: error: cannot guess build type; you must specify one Not here. > 5. after supplying that file, configure reports this error: > checking for xml2 library file... configure: WARNING: Can't find > xml2 library > README doesn't indicate where to find this library. Yep, exactly what I encountered too. > At this point, I gave up on that approach and tried the generic > script install. > > 6. My attempt to run wish install.tcl generates this error: > Error in startup script: extra characters after close-brace > while executing > "proc Slave_Component {slave type args" > (file "./install.tcl" line 306) > 7. After removing DOS ^M (thinking that was the problem), I continue > to get this error. There is a syntax error in install.tcl > (I reported this earlier, along with a fix - what happened to > that bug fix?) > > proc Slave_Component {slave type args}} { > should be > proc Slave_Component {slave type args} { > > 8. After fixing error, running install.tcl generates this error: > Build data file is missing. > Attempting to build from /vol/tclsrcsol/tcl84/tcldom-2.2/config.status > plus a tk dialog that says: > build status file Error > Warning: An error occured while parsing the build config status data. > No macros found Speculation: It seems as if the script install still does rely on the information provided by the configure script. > > I have no idea whether that is significant or not - if not, perhaps the > errors should not be generated. If so, then perhaps the README could > be updated to let someone know what to do about it? > > 9. After clicking on the okay button, the process continues and this error > appears: > Don't do "package require tcllib", ask for individual modules. > (Again, this is an error I submitted a fix for during the > previous release!) > > > 10. The tcldom installer appears, with this in its status window: > No files matching pattern "./docs/*.html" were found > Again - if this is not significant, perhaps it should not be displayed. > If it is significant, then something should be said about what to > do about it. > > 11. After cancelling that status window, the rest of the install > proceeded. > > I'm still uncertain about the purpose of the src and src-xml2 directories; > the README doesn't mention either. The src directory contains the generic tcldom sources. The framework where parsers etc can plug themselves into. src-libxml2 contains the glue code wrapping around libxml2 and making it useable by the tcldom framework in src. Essentially a separate package. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com Join Tcl'2002 in Vancouver http://www.tcl.tk/community/tcl2002/ ** Registration is open ** |