Thanks, David, for the quick turn-round.  I was hoping the thread would
engage you.  Previous build errors, zOS/OS400, aim back to you :)

The puzzler to me is that binding the Xerces objects statically fails, but
binding with my app succeeds !  Below is a snip of the failure and below the
failure is a snip showing the symbols found when I statically link the
Xerces .o files with my app (using traditional batch jcl) !  Your other
suggs re ICU and toolkit are good advice and I conclude my email with
comments.

FAILURE:

Building /u/agroccia/lewXerces/xerces-c-src_2_6_0/lib/libxerces-c2_6_0.dll
 IEW2456E 9207 SYMBOL __ct__Q2_11xercesc_2_220Iconv390TransServiceFv
UNRESOLVED.
          MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
FSUM3065 The LINKEDIT step ended with return code 8.
gmake[1]: ***
[/u/agroccia/lewXerces/xerces-c-src_2_6_0/lib/libxerces-c2_6_0.dll
] Error 3
Building
/u/agroccia/lewXerces/xerces-c-src_2_6_0/lib/libxerces-depdom2_6_0.dll
 IEW2456E 9207 SYMBOL
          fgArrayIndexOutOfBoundsException_Name__Q2_11xercesc_2_26XMLUni
          UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED


SUCCESS:

__ct__Q2_-viceFv := __ct__Q2_11xercesc_2_220Iconv390TransServiceFv

  $$DEMANGLED$$  ==
xercesc_2_2::Iconv390TransService::Iconv390TransService()     
fgArrayIn-XMLUni :=
fgArrayIndexOutOfBoundsException_Name__Q2_11xercesc_2_26XMLUni
  $$DEMANGLED$$  ==
xercesc_2_2::XMLUni::fgArrayIndexOutOfBoundsException_Name  


Yes, the toolkit is an option that has been used successfully.  It would be
helpful to know what the defaults taken to build the toolkit are
(transcoder,...).  In any event, we'd like to emulate our non-zOS brothers &
sisters, if possible, in our distribution, hence the desire to produce the
library ourselves.

I prefer, out of ignorance, aiming for a solution not involving ICU.  It's
been unclear (albeit thru cursory inspection only) how ICU fits.  All I saw
was the 8+MB distribution and saw a whole nother learning curve.

Thanks again, lew

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to