>> Nope, nor did I have to modify the xerces-c library (if you remember the >> problems we had before with isAnySlash) > > Oh! But aren't you still using the already modified library? If not > then that's good news...
Nope, I did a fresh unpack/compile of xerces-c-src_2_3_0 this morning. > Sorry, I actually meant running DOMPrint.pl by hand, but it's cool - > it's probably the same relative path error, so don't bother. Sorry, running DOMPrint.pl from samples works fine > Ok, the sourceforge compile farm is back online, so I'm going to see > about building it there (if not I'll get an account on the Apache OS X > machine). I need to get a C++ example that demonstrates the relative > path problems for the Xerces-C team so they can fix it. Let me know if there is anything else I can test. Cheers adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
