More extensive libxml2 test suites
Hi folks, Looking at the current instructions for libxml2 (simply because 2.6.21 was released today), it omits the more extensive test suites that are available from the W3C [0]. There's a test framework available in the xstc/ subdirectory of the tarball, into which one can place xsts-2002-01-16.tar.gz [1] and xsts-2004-01-14.tar.gz [2]. If Python is also available, when 'make check' is invoked, a whole barrage of XML Schema tests will be run (some of which fail here!). Is it worth mentioning these test suites at all? If so, I can knock up a patch to address this. Regards, Matt. [0]http://www.w3.org/XML/2004/xml-schema-test-suite/index.html [1]http://www.w3.org/XML/2004/xml-schema-test-suite/xmlschema2002-01-16/xsts-2002-01-16.tar.gz [2]http://www.w3.org/XML/2004/xml-schema-test-suite/xmlschema2004-01-14/xsts-2004-01-14.tar.gz -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: More extensive libxml2 test suites
Matthew Burgess wrote these words on 09/05/05 14:05 CST: Hi folks, Looking at the current instructions for libxml2 (simply because 2.6.21 was released today), it omits the more extensive test suites that are available from the W3C [0]. There's a test framework available in the xstc/ subdirectory of the tarball, into which one can place xsts-2002-01-16.tar.gz [1] and xsts-2004-01-14.tar.gz [2]. If Python is also available, when 'make check' is invoked, a whole barrage of XML Schema tests will be run (some of which fail here!). Is it worth mentioning these test suites at all? If so, I can knock up a patch to address this. In version 2.6.20, these files are downloaded automatically through the regular make check process. It then appears to do something, but I can't really tell by the logs. Is the procedure now different in that you must manually download these files before the make check is initiated? -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 15:01:00 up 156 days, 14:34, 3 users, load average: 0.69, 0.26, 0.14 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: More extensive libxml2 test suites
Randy McMurchy wrote:
Matthew Burgess wrote these words on 09/05/05 15:28 CST:
Oh, yeah, I see that now...I tried compiling libxml2 on a bare-bones LFS
system, hence didn't have `wget' installed yet! Is that worth
mentioning as a dependency (test-suite only, like `bc' is for openssl)?
Yes, definitely.
Just as a FYI type note, I missed this dependency originally, because
all that happens if one doesn't have `wget' around is that `make'
reports 'nothing to do for {all,check}' when in the xstc directory - it
doesn't even output a nice little warning that you might want to have
wget and python available to fully test the package. They're probably
mentioned in the README or similar, but honestly, who reads those things
anyway? :)
Well, it generates some test-scripts using python then runs them.
So, essentially, we just need to list the wget and python packages
as dependencies of the test suite, right?
Well, Python isn't *just* a dependency of the test suite of course (the
book already mentions that a Python module will be built if Python is
found), but yes , the full testsuite is dependent on having wget and
python around.
There isn't anything else we need to do though. Is this correct?
That's correct.
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
