You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(18) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(11) |
Feb
(2) |
Mar
(1) |
Apr
(4) |
May
(23) |
Jun
(17) |
Jul
(1) |
Aug
(17) |
Sep
(4) |
Oct
(14) |
Nov
(1) |
Dec
(2) |
2002 |
Jan
|
Feb
(2) |
Mar
(15) |
Apr
|
May
(19) |
Jun
(2) |
Jul
(8) |
Aug
(24) |
Sep
(21) |
Oct
(17) |
Nov
(11) |
Dec
(20) |
2003 |
Jan
(17) |
Feb
(19) |
Mar
(21) |
Apr
(13) |
May
(14) |
Jun
(7) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
2004 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
(5) |
Jul
(12) |
Aug
(3) |
Sep
(14) |
Oct
(1) |
Nov
(4) |
Dec
(3) |
2005 |
Jan
(1) |
Feb
(6) |
Mar
(3) |
Apr
|
May
(2) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
2006 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2007 |
Jan
(1) |
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(8) |
Oct
(1) |
Nov
|
Dec
|
From: alpesh <alp...@ho...> - 2002-07-10 03:03:23
|
You might get success on the tcl...@li... mailing list, but I think you essentially need to use TclXML with the newer versions of Tcl. The lack of a recent expect on Windows is a problem. ActiveState is prepared to do a port for anyone willing to fund it, but noone has been willing to foot the bill so far. Jeff Hobbs The Tcl Guy Senior Developer http://www.ActiveState.com/ Tcl Support and Productivity Solutions Join us in Sept. for Tcl'2002: http://www.tcl.tk/community/tcl2002/ > -----Original Message----- > From: alpesh [mailto:alp...@ho...] > Sent: July 4, 2002 10:14 PM > To: Je...@Ac... > Subject: Re: [ActiveTcl Bug 19791] Conflicts with TclXML > I agree tclsh80 is not a part of Active Tcl. But then expect > is not working with Tcl 8.3 / 4. I am using Win 2000. > Actually i wanted to use Tcl XML and Expect togather . what > are the ways out |
From: Derek F. <fo...@hu...> - 2002-07-09 08:55:10
|
On Tuesday 09 July 2002 1:26 am, you wrote: > Did Steve's clt-posted answer take care of you? Not really, no. :( Steve said the way to get a Doc Type is: ::dom::DOMImplementation createDocumentType token name publicid systemid If you don't want the public id, make it empty, eg: ::dom::DOMImplementation createDocumentType $doc product {} my.dtd Which I'd largely worked out from the source. With ActiveTcl-8.3.4.3 that gives me: wrong number of arguments, should be: DOMImplementation createDocumentType name publicid systemid while executing "::dom::DOMImplementation createDocumentType $doc "product" "" "testplan.dtd"" which, according to the code, is a valid error message. Steve's example gives 4 parameters, but the code only accepts 3. Internal usage of the CreateDocType routine in dom.tcl suggests 4 parameters is correct. I wouldn't claim to be good enough at Tcl to point and say "there's a bug in the interface code for ::dom::DOMImplementation createDocumentType", but something's not right. The issue of processing instructions also remains. Steve confirms the way to create one is ::dom::document createProcessingInstruction $parent target data which is what I'm using. The thing is, the processing instruction is only serialised if it's attached to an element node (which I found out by chance). Attaching it to a document node, which in my admittedly limited XML experience seems the natural thing to do, results in no processing instruction from the serialisation. Perhaps the PI handling code is missing in the serialisation code? Or perhaps this is by design and I don't understand the design. :-} And finally, the issue of colons in element names. Steve doesn't offer any advice here, so my "regsub -all" stays in place at the end of my script to get rid of them all. So, in short, no, I'm still struggling with TclDOM. In the short term I've hacked in some workarounds for the above issues which mean my script produces the XML I need. That's got the boss off my back. I'm hoping that when Steve gets back from his conference he'll be able to give me some more specific advice. -- 9:12am up 57 days, 1:17, 2 users, load average: 0.03, 0.03, 0.05 |
From: <Jef...@ca...> - 2002-07-05 08:01:01
|
I will be out of the office starting 07/03/2002 and will not return until 07/08/2002. please route eBA*SM questions to Jayesh or Marty. I'll return 7-8-02 wilbur.candle.com is offline until then |
From: Derek F. <fo...@hu...> - 2002-07-04 11:25:43
|
Me again. What gives you the idea I've just discovered this list? ;) I want a stylesheet processing instruction in my XML. Like this: <?xml-stylesheet type="text/xsl" href="ftpc.xsl"?> I'm calling dom::document createProcessingInstruction but no matter what parameters I give it, no such line comes out of the "serialize" call. How do I do it right? -- 12:22pm up 52 days, 4:27, 1 user, load average: 0.49, 0.16, 0.07 |
From: Derek F. <fo...@hu...> - 2002-07-04 11:22:10
|
When printing my DOM with "serialize" the elements have colons in them: <:product> blah blah </:product> This upsets my validator because the DTD doesn't have colons in the names. I'm assuming they're some form of default namespace indicator, but I never asked for them! How do I get rid of them (or work with them)? -- 12:19pm up 52 days, 4:25, 1 user, load average: 0.11, 0.10, 0.05 |
From: Derek F. <fo...@hu...> - 2002-07-04 11:19:57
|
I'm using TclDOM-2.0 shipped with Activestate Tcl, and although this is the first "from-scratch" DOM I've built, it's mostly going well. I've a problem right at the top though: I want to create the DOCTYPE line with the DTD in it. The result as printed from the "serialize" routine should be: <!DOCTYPE product SYSTEM "testplan.dtd"> So right at the top of my script I do: set doc [::dom::DOMImplementation create] ::dom::DOMImplementation createDocumentType $doc "" "testplan.dtd" set top [::dom::document createElement $doc "product"] but no matter how much I tinker with the line, I always get an error like: mismatch between root element type in document type declaration "SYSTEM" and root element "product" Can someone tell me what I'm doing wrong? -- 12:13pm up 52 days, 4:19, 1 user, load average: 0.04, 0.10, 0.05 |
From: Steve B. <Ste...@zv...> - 2002-06-19 11:26:17
|
Dear J=F6rg, You wrote: > I like to use expat and xerces together with tclxml but they are not > included in the download package of TclXML v2.1theta. I tried to instal= l a > precomiled version of expat for windows and to load the dll-libs direct= ly > but it's also not working. I've installed ActiveTcl 8.3 on Windows 2000 > Prof. >=20 > Is there someone to explain the correct proceeding to me? Firstly, the TclXML v2.1theta release is *Tcl-only*. It only has the pure-Tcl version of the XML parser. If you want a Windows binary of the expat interface then get ActiveTcl 8.4.0.1.beta2 from ActiveState. I never got the Xerces-C++ wrapper working, but instead I've got a working libxml2 wrapper for TclDOM. At the moment you need to checkout the CVS development tree to get access to it. Cheers, Steve Ball --=20 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 |
From: <Joe...@Be...> - 2002-06-19 10:57:31
|
Hello! I like to use expat and xerces together with tclxml but they are not included in the download package of TclXML v2.1theta. I tried to = install a precomiled version of expat for windows and to load the dll-libs = directly but it's also not working. I've installed ActiveTcl 8.3 on Windows 2000 Prof. Is there someone to explain the correct proceeding to me? Thanks, J=F6rg > Bertelsmann Distribution GmbH > J=F6rg Schmitz > Friedrich-Menzefricke-Str. 16-18 > 33775 Versmold >=20 > * fon +49-5241/80-1409 > * fax +49-5241/80-41866 > * email joe...@be... >=20 >=20 |
From: Larry W. V. <lv...@ca...> - 2002-05-24 18:32:21
|
Well, I _think_ I have fixed the problem. What appears to have been the problem was that one version of tcldom installed itself as tcldom-2.0 and a second version as tcldom2.0 . One was being updated by the make install process, but tcl's package processing was hitting the other version first, having a problem, and then stopping. -- Support Internet Radio <URL: http://saveinternetradio.org/ > 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. -><- |
From: Larry W. V. <lv...@ca...> - 2002-05-24 12:30:44
|
I have installed the tcl AND the c code from tcldom . When I attempt to use code which depends on tcldom being installed, I get errors saying that the code was unable to load the generic layer. If I load by hand the .so for the tcldom c implementation, then things at least get started (though I do get four errors from the tcldom test suite at that point). It appears that the tcldom package loading isn't loading the shared library. Could it be because when I built the tcldom shared library, it was built with --enable-symbols, and so the shared library is called tcldom2.0g.so instead of tcldom2.0.so ? The problem here is that I get the error about unable to load the generic layer, but no indication of what is going wrong... -- Support Internet Radio <URL: http://saveinternetradio.org/ > 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. -><- |
From: Mats B. <ma...@pr...> - 2002-05-21 06:39:30
|
Steve Ball wrote: > > Hi Mats, > > You wrote: > > I've put a patched TclXML (the 'tcl' parser class) archive (only tcl code) > > Downloaded the patch, but it would be alot easier for me to > do the next release if you could apply the patches yourself. > I'm only too happy to add you as a developer to the SourceForge > project - send me your SF login. > You seem to have more confidence in me than I have myself :-) The xml parser code is a very complex piece of code. Best would be if someone browsed through my changes, and ran the testsuit (which I haven't) to see there aren't any sideeffects I haven't figured out. My SF login in a separate post. /Mats |
From: Steve B. <Ste...@zv...> - 2002-05-20 10:50:23
|
Hi Mats, You wrote: > I've put a patched TclXML (the 'tcl' parser class) archive (only tcl code) Downloaded the patch, but it would be alot easier for me to do the next release if you could apply the patches yourself. I'm only too happy to add you as a developer to the SourceForge project - send me your SF login. 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 |
From: Mats B. <ma...@pr...> - 2002-05-18 13:03:42
|
Running the TclExpat parser using the script and data below crashes. I'm using tclexpat20.dll and tclxml20.dll from the ActiveState distro on Windows 2000. The crash is reproducible. When testing be sure that you are using the 'expat' parser class. The 'tcl' class works fine. Any ideas anyone? Mats Bengtsson -------------------------------------- package require xml 2.0 proc HandleStart {name attlist args} { if {[llength $attlist] > 0} { puts "==> (Start) '$name' has attributes '$attlist'" } else { puts "==> (Start) '$name'" } if {[llength $args]} {puts " args=$args"} } proc HandleEnd {name args} { global myParser puts "==> (End) '$name'" } proc HandleText {data} { puts "==> (Data) '$data'" } set parser [xml::parser] set classes [::xml::parserclass info names] $parser configure \ -final 0 \ -reportempty 1 \ -elementstartcommand HandleStart \ -elementendcommand HandleEnd \ -characterdatacommand HandleText \ -ignorewhitespace 1 \ -defaultexpandinternalentities 0 set data {<?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' id='3CE5FE2E' xmlns='jabber:client' from='athlon.se'>\ <iq type='result' id='1001'/>\ <iq type='result' id='1002' from='sg...@at.../home'><query xmlns='jabber:iq:roster'><item jid='ma...@at...' subscription='both'/></query></iq>\ <iq type='result' id='1003' from='sg...@at.../home' to='sg...@at.../home'/>\ <iq type='result' id='1004' to='sg...@at.../home' from='athlon.se'><service xmlns='jabber:iq:browse' type='jabber' jid='athlon.se' name='Jabber Server'>\ <service type='jud' jid='jud.athlon.se' name='Jabber User Directory'>\ <ns>jabber:iq:search</ns>\ <ns>jabber:iq:register</ns>\ </service>\ <conference type='public' jid='conference.athlon.se' name='Public Conferencing'/>\ </service></iq>\ <iq type='result' id='1005' to='sg...@at.../home' from='conference.athlon.se'><conference xmlns='jabber:iq:browse' type='public' name='Public Chatrooms'><conference type='public' jid='he...@co...' name='Assistance Zone (0)'/><conference type='public' jid='gi...@co...' name='Girls (0)'/><conference type='public' jid='ad...@co...' name='Adminz only (0)'/></conference></iq>\ <iq type='set'><query xmlns='jabber:iq:roster'><item jid='ko...@at...' subscription='none'/></query></iq>\ <iq type='result' id='1006' from='sg...@at.../home' to='sg...@at.../home'/><iq type='set'><query xmlns='jabber:iq:roster'><item jid='ko...@at...' subscription='none' ask='subscribe'/></query></iq>\ <presence to='sg...@at...' type='subscribe' from='ko...@at...'/>\ <presence to='sg...@at...' type='subscribed' from='ko...@at...'/><iq type='set'><query xmlns='jabber:iq:roster'><item jid='ko...@at...' subscription='to'/></query></iq><presence from='ko...@at.../home' to='sg...@at...'><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/></presence><presence to='sg...@at...' type='subscribe' from='ko...@at...'/>\ <presence from='ko...@at.../home' to='sg...@at...'><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/></presence>\ <presence from='ko...@at.../home' to='sg...@at...'><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/></presence><iq type='set'><query xmlns='jabber:iq:roster'><item jid='ko...@at...' subscription='both'/></query></iq>\ <presence from='ko...@at.../home' to='sg...@at...'><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/><x xmlns='jabber:x:delay' from='ko...@at.../home' stamp='20020518T07:10:47'/></presence>\ } $parser parse $data |
From: Mats B. <ma...@pr...> - 2002-05-18 13:03:25
|
I've put a patched TclXML (the 'tcl' parser class) archive (only tcl code) at "http://hem.fyristorg.com/matben/download/TclXML.tar.gz" It fixes three problems compared to the 2.1 theta distro: 1. A number of fixes related to the -final 0 option which is currently broken. With this patch you can take XML that is chopped off anywhere, and still parse it correctly. 2. A large number of error callbacks are now working. 3. Corrected a bug where a 'return -code 3', a code not TCL_OK, is detected also on the elementend callback and not only in the elementstart callback. Best Wishes, Mats Bengtsson |
From: Mats B. <ma...@pr...> - 2002-05-17 06:57:24
|
> From: Tobias Gabele <g....@be...> > > is there already a command somewhere in ::xml or ::sgml to quit parsing > based on an event. I want to stop parsing once a specific element occurs > in my elementstartcommand (to save execution time with lenghty xml files > when only one or few values have to be extracted). I could implement > this myself if its not there but maybe someone already came across the > same problem .. > You do return -code 3 (break) from your callback proc. Note a bug if made from element end callback (reported at SourceForge) Fix in sgml::ParseEvent:ElementClose proc: # Invoke callback #uplevel #0 $options(-elementendcommand) [list $tag] $empty $ns # Mats: # Shall be same as sgml::ParseEvent:ElementOpen set code [catch {uplevel #0 $options(-elementendcommand) [list $tag] $empty $ns} msg] #puts " sgml::ParseEvent:ElementClose (exit) state(stack)='$state(stack)'" #return {} return -code $code -errorinfo $::errorInfo $msg /Mats |
From: Steve B. <Ste...@zv...> - 2002-05-16 21:12:43
|
Tobias Gabele wrote: > i am using TclXML excessively in the ECOBAS project > (http://dino.wiz.uni-kassel.de/ecobas/new_db/download_sw.html) > and came across the following question: > > is there already a command somewhere in ::xml or ::sgml to quit parsing > based on an event. I want to stop parsing once a specific element occurs > in my elementstartcommand (to save execution time with lenghty xml files > when only one or few values have to be extracted). I could implement > this myself if its not there but maybe someone already came across the > same problem .. Your application can control the flow-of-control by returning a return code other than TCL_OK. Returning TCL_BREAK will halt the parser without throwing an exception (ie. 'return -code break'). See the documentation, or visit http://www.zveno.com/courses/samples/XML-App-Dev-Tcl/ 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 |
From: Tobias G. <g....@be...> - 2002-05-16 14:24:13
|
Hi all, i am using TclXML excessively in the ECOBAS project (http://dino.wiz.uni-kassel.de/ecobas/new_db/download_sw.html) and came across the following question: is there already a command somewhere in ::xml or ::sgml to quit parsing based on an event. I want to stop parsing once a specific element occurs in my elementstartcommand (to save execution time with lenghty xml files when only one or few values have to be extracted). I could implement this myself if its not there but maybe someone already came across the same problem .. -- With best regards, Tobias Gabele University of Kassel Faculty of Agriculture, International Rural Development and Environmental Protection (FB 11) Nordbahnhofstr. 1a D-37213 Witzenhausen (FRG) Phone: (+49)-5542-98-1609 or (+49)-36087-90618 or (+49)-30-83229749 Fax: (+49)-5542-98-1588 or (+49)-36087-90618 email: ga...@wi... |
From: Steve B. <Ste...@zv...> - 2002-05-09 21:15:57
|
Larry W. Virden wrote: > Just wanted to mention that the tcldom C code still does not compile on > SPARC Solaris 2.6. Yes, I can use the Tcl script version - I just thought > that if people are actually doing work on the C code they might want to know > it isn't compiling. I don't have access to a Solaris box anymore (except the SF compile farm) so it's a bit hard for me to check these things out. Having said that, please submit a bug report so that it's on my TODO (TOFIX?) list. > I also have one question - when doing the configure, I get a warning about not > being able to find "xml2" library - what is that? I don't see it mentioned > in the README file; if it is an external library, shouldn't it be mentioned? That's what the '--enable-xml2' switch on the command line is for... It refers to the Gnome libxml2 library, available from http://xmlsoft.org/. If it's not mentioned in the README then you could submit a documentation bug report. This library must be installed before attempting to build TclDOM/libxml2. 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 |
From: Larry W. V. <lv...@ca...> - 2002-05-09 17:11:26
|
$ cd tcldom/src $ $PWD/configure --prefix=/usr/tcl84 --enable-shared --enable-symbols creating cache ./config.cache checking for Tcl configuration... found /vol/tclsrcsol/tcl84/tcl/unix/tclConfig. sh checking for existence of /vol/tclsrcsol/tcl84/tcl/unix/tclConfig.sh... loading checking for Tcl public headers... /usr/tcl84/include checking for expat library... -L/usr/tcl84/lib -lexpat0.2 checking for gcc... cc checking whether the C compiler (cc ) works... yes checking whether the C compiler (cc ) is a cross-compiler... no checking whether we are using GNU C... no checking whether cc accepts -g... yes checking for a BSD compatible install... /projects/gnu/sparc-sun-solaris2.6/bin/ ginstall -c checking for Cygwin environment... no checking for object suffix... o checking for mingw32 environment... no checking for executable suffix... no checking for tclsh... /usr/tcl84/bin/tclsh8.4 checking for build with symbols... yes checking how to build libraries... shared updating cache ./config.cache creating ./config.status creating Makefile creating pkgIndex.tcl $ make all cc -DPACKAGE_NAME=\"tcldom\" -DVERSION=\"2.0\" -DPATCHLEVEL=\"1\" -DUSE_TCL_STUB S=1 -I"/usr/tcl84/include" -g -c tcldompro.c -o tcldompro.o "tcldompro.c", line 461: warning: statement not reached "tcldompro.c", line 907: warning: statement not reached "tcldompro.c", line 1120: warning: statement not reached "tcldompro.c", line 1303: warning: statement not reached "tcldompro.c", line 1415: warning: statement not reached "tcldompro.c", line 1696: warning: statement not reached "tcldompro.c", line 1842: warning: statement not reached "tcldompro.c", line 2158: warning: statement not reached "tcldompro.c", line 2248: warning: statement not reached "tcldompro.c", line 2327: warning: statement not reached cc -DPACKAGE_NAME=\"tcldom\" -DVERSION=\"2.0\" -DPATCHLEVEL=\"1\" -DUSE_TCL_STUB S=1 -I"/usr/tcl84/include" -g -c tdpExpat.c -o tdpExpat.o "tdpExpat.c", line 1073: warning: statement not reached cc -DPACKAGE_NAME=\"tcldom\" -DVERSION=\"2.0\" -DPATCHLEVEL=\"1\" -DUSE_TCL_STUB S=1 -I"/usr/tcl84/include" -g -c traversal.c -o traversal.o "traversal.c", line 1135: warning: statement not reached cc -DPACKAGE_NAME=\"tcldom\" -DVERSION=\"2.0\" -DPATCHLEVEL=\"1\" -DUSE_TCL_STUB S=1 -I"/usr/tcl84/include" -g -c livelist.c -o livelist.o "livelist.c", line 124: warning: argument #4 is incompatible with prototype: prototype: pointer to function(pointer to void, pointer to struct Tcl_In terp {pointer to char result, pointer to function(pointer to char) returning voi d freeProc, int errorLine}, pointer to char, pointer to const char, int) returni ng pointer to char : "unknown", line 0 argument : pointer to function(pointer to void, pointer to struct Tcl_In terp {pointer to char result, pointer to function(pointer to char) returning voi d freeProc, int errorLine}, pointer to char, pointer to char, int) returning poi nter to char rm -f tcldom2.0g.so /usr/ccs/bin/ld -G -z text -o tcldom2.0g.so \ tcldompro.o tdpExpat.o traversal.o livelist.o -L/usr/tcl84/lib -lexpat0. 2 -L/usr/tcl84/lib -ltclstub8.4g -L/usr/tcl84/lib -ltclstub8.4g Text relocation remains referenced against symbol offset in file <unknown> 0x1c tcldompro.o and errors go on for over 2000 more lines <unknown> 0x21dc tcldompro.o <unknown> 0x21e0 tcldompro.o <unknown> 0x21e4 tcldompro.o <unknown> 0x21e8 tcldompro.o <unknown> 0x21ec tcldompro.o <unknown> 0x2c38 tcldompro.o <unknown> 0x5b6c tcldompro.o <unknown> 0x2c3c tcldompro.o ld: fatal: relocations remain against allocatable but non-writable sections make: *** [tcldom2.0g.so] Error 1 -- Support Internet Radio <URL: http://saveinternetradio.org/ > 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. -><- |
From: Joe E. <jen...@fl...> - 2002-05-09 14:22:31
|
Larry W. Virden wrote: > > Just wanted to mention that the tcldom C code still does not compile on > SPARC Solaris 2.6. [...] > > I configure with this command: > $ cd tcldom > $ $PWD/configure --prefix=/usr/tcl84 --enable-symbols --enable-shared --enable-xml2 Could you try this in the 'tcldom/src' directory instead? I think that should work. > I also have one question - when doing the configure, I get a warning about not > being able to find "xml2" library - what is that? I don't see it mentioned > in the README file; if it is an external library, shouldn't it be mentioned? That should be the GNOME xml library, available from <URL: http://xmlsoft.org > --Joe English jen...@fl... |
From: Larry W. V. <lv...@ca...> - 2002-05-09 11:14:28
|
Just wanted to mention that the tcldom C code still does not compile on SPARC Solaris 2.6. Yes, I can use the Tcl script version - I just thought that if people are actually doing work on the C code they might want to know it isn't compiling. I also have one question - when doing the configure, I get a warning about not being able to find "xml2" library - what is that? I don't see it mentioned in the README file; if it is an external library, shouldn't it be mentioned? I configure with this command: $ cd tcldom $ $PWD/configure --prefix=/usr/tcl84 --enable-symbols --enable-shared --enable-xml2 creating cache ./config.cache checking for gcc... cc checking whether the C compiler (cc ) works... yes checking whether the C compiler (cc ) is a cross-compiler... no checking whether we are using GNU C... no checking whether cc accepts -g... yes checking for a BSD compatible install... /projects/gnu/sparc-sun-solaris2.6/bin/ ginstall -c checking whether make sets ${MAKE}... yes checking for ranlib... ranlib checking for Cygwin environment... no checking for object suffix... o checking for mingw32 environment... no checking for executable suffix... no checking for Tcl configuration... found /vol/tclsrcsol/tcl84/tcl/unix/tclConfig. sh checking for existence of /vol/tclsrcsol/tcl84/tcl/unix/tclConfig.sh... loading checking for xml2 library file... configure: warning: Can't find xml2 library checking for tclsh... /usr/tcl84/bin/tclsh8.4 checking for tclstub library... -L/usr/tcl84/lib -ltclstub8.4t checking for building with threads... no (default) checking how to build libraries... shared checking for build with symbols... yes updating cache ./config.cache creating ./config.status creating Makefile creating src-libxml2/Makefile creating library/pkgIndex.tcl $ make all cc -DVERSION=\"2.0\" -DUSE_TCL_STUBS=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DTC L_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_DIRENT64=1 -DHAVE_STRUCT_STAT64=1 -DHAV E_TYPE_OFF64_T=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL= 1 -DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DHAVE_UNI STD_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_T ZNAME=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_ST_B LKSIZE=1 -DSTDC_HEADERS=1 -DNO_UNION_WAIT=1 -DNEED_MATHERR=1 -DHAVE_SIGNED_CHAR= 1 -DHAVE_LANGINFO=1 -D_REENTRANT=1 -D_POSIX_PTHREAD_SEMANTICS=1 -DHAVE_SYS_IOCTL _H=1 -DHAVE_SYS_FILIO_H=1 -I/usr/tcl84/include -g -KPIC -c `echo /vol/ tclsrcsol/tcl84/tcldom/tcldom.c` -o tcldom.o "/vol/tclsrcsol/tcl84/tcldom/tcldom.c", line 210: warning: argument #3 is incomp atible with prototype: prototype: pointer to pointer to const char : "unknown", line 0 argument : pointer to pointer to char "/vol/tclsrcsol/tcl84/tcldom/tcldom.c", line 285: warning: argument #3 is incomp atible with prototype: prototype: pointer to pointer to const char : "unknown", line 0 argument : pointer to pointer to char rm -f libtcldom2.0.so /usr/ccs/bin/ld -G -z text -o libtcldom2.0.so tcldom.o -L/usr/tcl84/lib -ltclst ub8.4t : libtcldom2.0.so cd src-libxml2; make make[1]: Entering directory `/vol/tclsrcsol/tcl84/tcldom/src-libxml2' cc -DVERSION=\"2.0\" -DUSE_TCL_STUBS=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DTC L_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_DIRENT64=1 -DHAVE_STRUCT_STAT64=1 -DHAV E_TYPE_OFF64_T=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL= 1 -DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DHAVE_UNI STD_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_T ZNAME=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_ST_B LKSIZE=1 -DSTDC_HEADERS=1 -DNO_UNION_WAIT=1 -DNEED_MATHERR=1 -DHAVE_SIGNED_CHAR= 1 -DHAVE_LANGINFO=1 -D_REENTRANT=1 -D_POSIX_PTHREAD_SEMANTICS=1 -DHAVE_SYS_IOCTL _H=1 -DHAVE_SYS_FILIO_H=1 -I/usr/local/include/libxml2 -g -KPIC -I/vol /tclsrcsol/tcl84/tcldom -c `echo /vol/tclsrcsol/tcl84/tcldom/src-libxml2/tcldom- libxml2.c` -o tcldom-libxml2.o "/vol/tclsrcsol/tcl84/tcldom/tcldom.h", line 23: cannot find include file: <tcl. h> "/vol/tclsrcsol/tcl84/tcldom/tcldom.h", line 80: syntax error before or at: Tcl_ Obj "/vol/tclsrcsol/tcl84/tcldom/tcldom.h", line 80: cannot recover from previous er rors cc: acomp failed for /vol/tclsrcsol/tcl84/tcldom/src-libxml2/tcldom-libxml2.c make[1]: *** [tcldom-libxml2.o] Error 2 make[1]: Leaving directory `/vol/tclsrcsol/tcl84/tcldom/src-libxml2' make: *** [libtcldom-libxml2-2.0.so] Error 2 -- Support Internet Radio <URL: http://saveinternetradio.org/ > 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. -><- |
From: Steve B. <Ste...@zv...> - 2002-05-07 21:20:38
|
Larry W. Virden wrote: > I've got the latest tclxml from the CVS repository, and installed it > with my Tcl 8.4 environment. > > In the examples directory, the README says: > > REC-xml-20001006.xml > The W3C XML spec in XML format. A handy file to run xmlwc over > to test your build. You should get this output with the command > tclsh8.3 xmlwc REC-xml-20001006.xml > : > > 2929 14978 116827 REC-xml-20001006.xml > > However, I am seeing this: > > $ tclsh8.4 ./xmlwc REC-xml-20001006.xml > 2954 14966 117568 REC-xml-20001006.xml > $ ls -l *xml > -rwxr-xr-x 1 lwv26 dept26 201918 Dec 28 2000 REC-xml-20001006.xml > > Since the numbers are differing so wildly, I thought I would ask here and > see if anyone else had actually tried this all out. I get the same numbers. To verify, I ran the document through an empty XSL stylesheet. This strips the markup. Then I removed the XML declaration, resulting in a completely plain text file. wc produces: [localhost:~/tclxml-main/examples] steve% wc stripped.txt 2951 17360 121252 stripped.txt Fewer lines, but more words and characters. I'll look into it a bit further. One thing to do is save the text being counted by xmlwc and then compare against the text file generated above. BTW, I often use this program when writing papers and articles that have a word limit, so I have an interest in making sure that it is accurate. 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 |
From: Larry W. V. <lv...@ca...> - 2002-05-07 16:04:31
|
Hi! I've got the latest tclxml from the CVS repository, and installed it with my Tcl 8.4 environment. In the examples directory, the README says: REC-xml-20001006.xml The W3C XML spec in XML format. A handy file to run xmlwc over to test your build. You should get this output with the command tclsh8.3 xmlwc REC-xml-20001006.xml : 2929 14978 116827 REC-xml-20001006.xml However, I am seeing this: $ tclsh8.4 ./xmlwc REC-xml-20001006.xml 2954 14966 117568 REC-xml-20001006.xml $ ls -l *xml -rwxr-xr-x 1 lwv26 dept26 201918 Dec 28 2000 REC-xml-20001006.xml Since the numbers are differing so wildly, I thought I would ask here and see if anyone else had actually tried this all out. -- Support Internet Radio <URL: http://saveinternetradio.org/ > 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. -><- |
From: P. E. C. <ec...@ci...> - 2002-05-07 00:09:12
|
Thnaks Steve. This solved the problem. Could you point me there are more example? I didn't quite get the idea after read the included document. Eric. At 12:37 PM 5/5/2002 +1000, Steve Ball wrote: >P. Eric Chi wrote: >>After I download and install tcllib 1.2, the TclXML install.tcl still >>says, "Package tcllib version 0.8 is required by TclXML, but is not >>installed. ..." >>I have set TCLLIBPATH=/usr/local/lib/tnm2.1.9 >>/usr/local/lib/tkined1.4.9 /usr/local/lib/tcllib1.2 >>Is ther eother environment variable I should set or how to let the >>TclXml know the tcllib is already there/ > >The problem with tcllib is fixed in the CVS repository, >but I haven't made a new release yet that contains the fix. > >In order to fix the current version, edit the install.data >file in the source directory. Change the 'Require tcllib' >line. > >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 |
From: <Jef...@ca...> - 2002-05-06 08:00:52
|
I will be out of the office starting 04/20/2002 and will not return until 05/08/2002. please route eBA*SM questions to Jayesh or Marty, QoS to Perry Gibson, otherwise I'll wade thru the email when I return :-) |