On 7 Oct 01, Jason E. Stewart writes: > Hey All, > > I'm pleased to announce the new release of XML::Xerces. Because of big > improvements in SWIG, I've been able to really simplify how the code > is generated, and that should help porting to different > architectures. > > One big issue that has made porting dificult is my bad choice of using > the standard C++ iostream cerr in many of the error reporters. This > created all sorts of problems between gcc's implementation and other > compiler vendor's implementations. Instead I now use the Perl's > builtin croak() method. So I'm hoping this reducing a lot of > relocation and linking problems that people have reported.
Jason, I have a couple of things to report, which are separate but related. Apologies for the length of this message. I'm completely ignorant of both MakeMaker and C++ (what I'm writing about), but here goes... This is Compaq Tru64 UNIX V5.0A (Rev. 1094), building XML-Xerces-1.5.7 for perl5.00503, against xerces-c-src_2001-10-05. Both perl and xerces-c were built with gcc-2.95.3. Before editing hints/dec_osf1.pl, here is the output of "perl Makefile.PL": > Using XERCES_LIB = /sw/common/src/xerces-c_2001-10-05/alpha-osf1/lib > Using XERCES_INCLUDE = /sw/common/src/xerces-c_2001-10-05/alpha-osf1/include > Checking to see if libxerces is in your library path...Use of uninitialized value at >(eval 24) line 98. > Use of uninitialized value at (eval 36) line 74. > Use of uninitialized value at (eval 36) line 75. > Use of uninitialized value at (eval 36) line 76. > Use of uninitialized value at (eval 36) line 89. > Use of uninitialized value at (eval 67) line 14. > Use of uninitialized value at (eval 67) line 15. > Use of uninitialized value at (eval 67) line 16. > Use of uninitialized value at (eval 67) line 17. > Use of uninitialized value at (eval 67) line 19. > Use of uninitialized value at (eval 67) line 20. > Use of uninitialized value at (eval 67) line 21. > Use of uninitialized value at (eval 67) line 22. > Use of uninitialized value at (eval 67) line 34. > Use of uninitialized value at (eval 67) line 43. > Success!! > Using Xerces-C version: 1.5.1 > Checking if your kit is complete... > Looks good > Processing hints file hints/dec_osf.pl > 'CC' is not a known MakeMaker parameter name. > 'CCFLAGS' is not a known MakeMaker parameter name. > 'LD' is not a known MakeMaker parameter name. > 'PREREQ_PM' is not a known MakeMaker parameter name. > Warning: Guessing NAME [alpha-osf1] from current directory name. > Writing Makefile for XML::Xerces::DOMParse > Writing Makefile for Handler > Checking if your kit is complete... > Looks good > Processing hints file hints/dec_osf.pl > Writing Makefile for XML::Xerces::DOMParse > Writing Makefile for XML::Xerces Notice how hints/dec_osf.pl is processed twice, but seems not to make sense of it the first time. In my case, since perl was built with gcc but hints/dec_osf1.pl sepecifies cxx, I find that Handler/Makefile uses gcc, but Xerces.C is compiled with cxx. Does that make sense? I have no idea how to read Makefile.PL files, sorry! After commenting out the cxx definitions in hints/dec_osf1.pl (since gcc should be able to handle C++ code), I get the following error in "make": > gcc -c -I. -IHandler -I/sw/common/src/xerces-c_2001-10-05/alpha-osf1/include >-D_REENTRANT -DHAS_BOOL -O3 -DVERSION=\"1.5.7\" -DXS_VERSION=\"1.5.7\" -fpic >-I/sw/common/share/perl/5.00503/alpha-osf1/CORE Xerces.C > Xerces.C: In function `struct swig_type_info * SWIG_TypeCheck(SV *, swig_type_info >*)': > Xerces.C:175: passing `const char *' as argument 2 of `Perl_sv_derived_from(SV *, >char *)' discards qualifiers > make: *** [Xerces.o] Error 1 Is that a problem with my configuration or with Xerces.C? Thanks for your help. Regards, David ------------------------------------------------------------------- David Starks-Browning | [EMAIL PROTECTED] EMBL Outstation -- | The European Bioinformatics Institute | Wellcome Trust Genome Campus | tel: +44 (1223) 494 616 Hinxton, Cambridge, CB10 1SD, UK | fax: +44 (1223) 494 468 ------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
