You are viewing a plain text version of this content. The canonical link for it is here.
Posted to p-dev@xerces.apache.org by "Steven N. Hirsch" <hi...@btv.ibm.com> on 2001/11/05 20:43:57 UTC
AIX 4.3.3 Build problems
All,
First, to have any hope of linking correctly against the xerces library,
this needs to happen:
--------------------------- Cut Here -----------------------------------
--- XML-Xerces-1.5.2_0/hints/aix.pl.orig Fri Oct 26 21:40:49 2001
+++ XML-Xerces-1.5.2_0/hints/aix.pl Mon Nov 5 13:27:07 2001
@@ -1,4 +1,4 @@
-$self->{macro}= "-DHAS_BOOL -Dbool=int";
+$self->{CCFLAGS} .= " -DHAS_BOOL -Dbool=int";
__END__
This was derived from the following email:
--------------------------- Cut Here ---------------------------------
I don't know what 'macro' is intended to do, but the defines fail to make
it into the appropriate build commands without the above fix.
Once that's done it will link. The bad news is that many tests fail:
make[1]: Entering directory `/home/hirschs/XML-Xerces-1.5.2_0/DOMParse'
make[1]: Leaving directory `/home/hirschs/XML-Xerces-1.5.2_0/DOMParse'
PERL_DL_NONLAZY=1 /afs/btv.ibm.com/u4/hirschs/local/bin/perl -Iblib/arch -Iblib/lib -I/afs/btv.ibm.com/u4/hirschs/local/lib/perl5/5.6.0/aix -I/afs/btv.ibm.com/u4/hirschs/local/lib/perl5/5.6.0 -e 'use Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
t/AttributeList.....ok
t/Attributes........ok
t/DOMCount..........ok
t/DOMCreate.........ok
t/DOMException......dubious
Test returned status 0 (wstat 139, 0x8b)
test program seems to have generated a core
DIED. FAILED tests 2, 4-7
Failed 5/7 tests, 28.57% okay
t/DOMParser.........ok
t/DOMPrint..........ok
t/DOM_Attr..........ok
t/DOM_Document......ok
t/DOM_Element.......ok
t/DOM_Entity........ok 1/3 Failed test 3 as expected, no worries
t/DOM_Entity........ok
t/DOM_NamedNodeMap..ok
t/DOM_Node..........ok
t/DOM_NodeList......ok
t/EntityResolver....ok
t/IDOMCount.........ok
t/IDOMParser........ok
t/IDOMPrint.........ok
t/IDOM_Attr.........ok
t/IDOM_DOMException.ok 7/7FAILED tests 2-3, 6
Failed 3/7 tests, 57.14% okay
t/IDOM_Document.....ok 35124/35124FAILED tests 3-4
Failed 2/35124 tests, 99.99% okay
t/IDOM_Element......ok
t/IDOM_Entity.......ok 1/3 Failed test 3 as expected, no worries
t/IDOM_Entity.......ok
t/IDOM_NamedNodeMap.ok
t/IDOM_Node.........ok
t/IDOM_NodeList.....ok
t/InputSource.......ok
t/LocalFileInputSource.ok
t/MemBufInputSource.ok
t/PerlErrorHandler..ok
t/SAX2Count.........ok
t/SAXCount..........ok
t/SAXException......dubious
Test returned status 0 (wstat 139, 0x8b)
test program seems to have generated a core
DIED. FAILED tests 2-6
Failed 5/6 tests, 16.67% okay
t/SAXParser.........ok
t/Schema............ok
t/StdInInputSource..ok
t/URLInputSource....dubious
Test returned status 0 (wstat 132, 0x84)
test program seems to have generated a core
DIED. FAILED tests 7-9
Failed 3/9 tests, 66.67% okay
t/XMLException......NOK 5FAILED test 5
Failed 1/5 tests, 80.00% okay
t/XMLURL............ok
t/XMLUri............ok
t/actualCast........ok
t/domTest...........ok
Failed Test Status Wstat Total Fail Failed List of failed
-------------------------------------------------------------------------------
t/DOMException. 0 139 7 5 71.43% 2, 4-7
t/IDOM_DOMExcep 7 3 42.86% 2-3, 6
t/IDOM_Document 35124 2 0.01% 3-4
t/SAXException. 0 139 6 5 83.33% 2-6
t/URLInputSourc 0 132 9 3 33.33% 7-9
t/XMLException. 5 1 20.00% 5
Failed 6/42 test scripts, 85.71% okay. 19/70494 subtests failed, 99.97% okay.
make: *** [test_dynamic] Error 2
I'm getting very discouraged. This is two-for-two on failed build
attempts (see earlier posting about Linux problems.)
I don't mind rolling up my sleeves and debugging, but I'd like to know
what the status is supposed to be, i.e., if this is expected to pass all
tests I'll see if my environment is broken before digging through the
sources.
I'm working on a box running AIX 4.3.3 with xlC 3.6.6.0
Steve
--
----------------------------------------------------------------
Steven N. Hirsch tie-line: 446-6557 ext: 802-769-6557
Staff Engineer Methodology Integration Team
ASIC Product Development IBM Microelectronics
----------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-p-dev-help@xml.apache.org
Re: AIX 4.3.3 Build problems
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
"Steven N. Hirsch" <hi...@btv.ibm.com> writes:
> First, to have any hope of linking correctly against the xerces library,
> this needs to happen:
>
> --------------------------- Cut Here -----------------------------------
> --- XML-Xerces-1.5.2_0/hints/aix.pl.orig Fri Oct 26 21:40:49 2001
> +++ XML-Xerces-1.5.2_0/hints/aix.pl Mon Nov 5 13:27:07 2001
> @@ -1,4 +1,4 @@
> -$self->{macro}= "-DHAS_BOOL -Dbool=int";
> +$self->{CCFLAGS} .= " -DHAS_BOOL -Dbool=int";
>
> __END__
> This was derived from the following email:
> --------------------------- Cut Here ---------------------------------
>
> I don't know what 'macro' is intended to do, but the defines fail to make
> it into the appropriate build commands without the above fix.
Doh! My fault. Not only was it a syntax error,('macro' takes a hash
reference) but it doesn't work anyway. I've made your change, thanks.
> Once that's done it will link. The bad news is that many tests
> fail:
Are you using the AIX binaries? If so, please compile from source.
Also, you're not universally dumping core like you were on RH, you're
failing specific tests that should have caused exceptions, but
didn't...
If you could run the tests without Test::Harnes and send the output it
would be useful. From within the toplevel XML-Xerces directory use;
perl -w -Mblib t/DOMException.t
for the tests that are failing. Test::Harness steals STDOUT and so you
miss some useful info.
> t/DOMException. 0 139 7 5 71.43% 2, 4-7
> t/IDOM_DOMExcep 7 3 42.86% 2-3, 6
> t/IDOM_Document 35124 2 0.01% 3-4
> t/SAXException. 0 139 6 5 83.33% 2-6
> t/URLInputSourc 0 132 9 3 33.33% 7-9
> t/XMLException. 5 1 20.00% 5
> I'm getting very discouraged. This is two-for-two on failed build
> attempts (see earlier posting about Linux problems.)
I hear you. Sorry about this. Right now portability is the biggest
pain about this project. This happens because Perl doens't track your
C++ compiler information, just the info for your C compiler. I have a
method that I believe will fix this (i.e. reading all C++ compiler
info from the Xerces-C config.status file), but I need time.
> I don't mind rolling up my sleeves and debugging, but I'd like to know
> what the status is supposed to be, i.e., if this is expected to pass all
> tests I'll see if my environment is broken before digging through the
> sources.
>
> I'm working on a box running AIX 4.3.3 with xlC 3.6.6.0
Honestly, this sounds like a portability issue not anything that you
could fix with a debugger. What would help is compiling Xerces from
source and comparing the compile lines from Xerces.C to the lines from
one of the Xerces-C++ files.
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-p-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-p-dev-help@xml.apache.org