tclxml-users

[Tclxml-users] Report of my attempt to install tcldom 2.2

[Larry W. V. <lv...@ca...>]

1. The activestate cvs snapshot does not apparently reflect tcldom 2.2 -
anyone know why?
2. The sf.net tar file didn't include top level configure -
is configure supposed to be done elsewhere?  The README isn't clear.
3. After I ran autoconf to create the configure, configure reports this error:
configure: error: cannot run /bin/ksh config/config.sub
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
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.

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

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.
-- 
Tcl'2002 Sept 16, 2002, Vancouver, BC http://www.tcl.tk/community/tcl2002/
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

Re: [Tclxml-users] Report of my attempt to install tcldom 2.2

[Steve B. <Ste...@zv...>]

Larry W. Virden wrote:
> 1. The activestate cvs snapshot does not apparently reflect tcldom 2.2 -
> anyone know why?

You would have to ask ActiveState.  I imagien they need
a little time to integrate it.

> 2. The sf.net tar file didn't include top level configure -
> is configure supposed to be done elsewhere?  The README isn't clear.

Oops.  I'll make sure the next release includes configure.

> 3. After I ran autoconf to create the configure, configure reports this error:
> configure: error: cannot run /bin/ksh config/config.sub
> 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
> 5. after supplying that file, configure reports this error:
> checking for xml2 library file... configure: WARNING: Can't find xml2 library

What can I say?  I use ProjectBuilder under MacOSX to compile
all of this stuff.  It works for me ;-)  If someone would like
to contribute fixes to the autoconf files then I will gladly
accept them.

> README doesn't indicate where to find this library.

The website lists the dependencies.  I have updated the
README with the libxml2 URL.

> 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)

Sigh.  I thought that was fixed some time ago.  Now fixed.

> 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} {

See above.

> 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

Hmmm.  Someone will need to investigate that further... Pete?

> 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!)

That must be a leftover from TclXML - TclDOM doesn't use any
tcllib modules itself.  I have removed that line from install.data.

> 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.

That's not significant, but I will make sure that the nroff and HTML
versions of the man page are in the next release.

> 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.

I've added a MANIFEST file.

I'm working on a v2.3 release to fix these problems,
but have to get the Tcl2K2 paper written first ;-)

Cheers,
Steve Ball

-- 
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