[EMAIL PROTECTED] writes: > --=_alternative 001241498525724E_= > Content-Type: text/plain; charset="US-ASCII" > > We need to build Xerces-C version 1.6 on an HP-UX 11, Itanium machine.
1.6 is a really old version of Xerces-C++. I don't think IA-64 existed when it was released. You may want to consider upgrading to Xerces-C++ 2.7.0. > After > several attempts, all of the code seemed to be built. But, when the linker > is attempting > to create the library, there are numerous "unsatisifed symbol" errors. > They > all appear to be for methods which are in classes that reside in the > $XERCESROOT/src/util directory. However, none of the files which seem to > be resulting in > unsatisfied symbols are built when the util directory is built. All of the > .cpp files in that directory are built, and the > .o(s) are copied to the lib/HPUX directory. But none of the .c extension > files are built. The .C files (at least in 2.7.0) contain template definitions and are normally included in the corresponding header files. One reason you could get those unresolved symbols is when the .C files are actually not included, for example, because of a missing preprocessor definition. The XERCES_TMPLSINC define in the command line you provided look relevant. hth, -boris -- Boris Kolpackov Code Synthesis Tools CC http://www.codesynthesis.com Open-Source, Cross-Platform C++ XML Data Binding
