Hello, Instead of using -xxlC_r, try using -xxlCcore_r . the xlCcore_r (and xlCcore) commands are provided by xlC to allow the use of standard libraries other than the default. You may have to do the same thing when building your Xerces-C library.
Cheers, Neil Neil Graham Manager, XSLT Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] David Bertoni <[EMAIL PROTECTED]> 06/08/07 11:18 AM Please respond to [email protected] To [email protected] cc Subject Re: Problem with cout when linking Xerces libs into executable [EMAIL PROTECTED] wrote: > > Hi all, > > I've compiled xerces 2.7 using xlC 7.0 on AIX 5.3. The Xerces libraries > were created using: > runConfigure -paix -cxlc_r -xxlC_r > > However, any time I link the Xerces libraries into an executable, cout > no longer works. > > Example: > > #include <iostream> > > int main(int argC, char* argV[]) > { > std::cout << "Hello world\n" << std::endl; > > return 0; > } > > The above program works fine without Xerces libraries linked in. As soon > as the libraries are linked, I get the following error and the program > cores: > > /app/sourcepro/Ed9/include/rw/_ioinsert.cc:116: Assertion '0 != > __strm.rdbuf ()' failed. > > ( we are using Roguewave libraries in our app) But the xlC compiler has its own version of the standard library from Dinkunware. Are you sure you can mix the two? You might need to make the necessary changes to the Xerces-C makefiles to have Xerces-C also the Rogue Wave version. Dave Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
