[EMAIL PROTECTED] (Jason E. Stewart) writes:
> From: John Chatzidimitriou <[EMAIL PROTECTED]>
> Subject: Trying to compile xerces-p with forte 7 on Solaris 8
> To: [EMAIL PROTECTED]
> Date: Wed, 08 Jun 2005 12:35:50 +0300
>
> Dear Jason,
>
> I have managed to compile XML-Xerces-2.6.0-0 and XML-Xerces-2.5.0-0
> on Solaris 8 using GCC 2.95 and
> Perl 5.8.6.
So you were able to build the 2.6 snapshot? Did it work out-of-the box
or did you need to modify Makefile.PL?
I would give up on 2.5 and use 2.6. I will make a second snapshot by
the end of the week.
2.5 is buggy and has a number of *sever* memory leaks.
> The problem is when I am trying to compile the XML-Xerces
> using the Forte 7 CC compiler.
> I have found your article about the operator>>(char&) and how to add
>
> #ifdef bool
> #undef bool
> #endif /* bool */
If you needed to make any modifications to Xerces files, let me know
what files and what mods, I will include them in the solaris hints
file, so that it should work out-of-the box for others.
> in Xerces.cpp. After that I did a recompilation with CC and everything
> was OK until I made gmake test, where all tests failed. The output I
> got for almost all the tests is
> .Can't load
> '/home1/jxatz/install/XML-Xerces-2.5.0-0/blib/arch/auto/XML/Xerces/Xerces.so'
> for module XML::Xerces: ld.so.1: /home1/jxatz/ED_Perl_5.8.6/bin/perl:
> fatal: relocation error: file
> /home1/jxatz/install/XML-Xerces-2.5.0-0/blib/arch/auto/XML/Xerces/Xerces.so:
> symbol
> __1cLxercesc_2_5UNameIdPoolEnumerator4n0AODTDElementDecl__2t6Mrk1_v_:
> referenced symbol not found at
> /home1/jxatz/ED_Perl_5.8.6/lib/perl5/5.8.6/sun4-solaris/DynaLoader.pm
> line 230.
> at /home1/jxatz/install/XML-Xerces-2.5.0-0/blib/lib/XML/Xerces.pm line 7
>
> But when I run the test from the command line most of them succeed
>
> Is this an alert factor? Is there a way to fix the problem so that the
> tests succeed?
make test runs the command:
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" \
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
the test harness is setup to be very strict, for example, it forces
that *all* symbols be loaded from all dynamic libraries - so if your
.so has *any* unresolvable symbols loading will fail.
But if you simply run the tests scripts by hand:
perl -Mblib -w t/*.t
then the tests will run just fine if there is an unresolvable symbol
that is never used.
That is my guess as to what you are experiencing.
Cheers,
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
