Graham Bennett wrote:
shouldn't 'configure CC=g++' do the job just fine ?Sounds reasonable, but I then get:checking for g++ option to accept ANSI C... no... configure: error: Compiler not ANSI compliant
ah, the joy of autoconf...:-/ I remember running into problems with configure tests when done with a C++ compiler instead of C. The problems were related to tests not being correct C++ code. The autoconf m4 macros are full of them. :-( Well, what I tried to point out was merely that you should build libxml2 with a C++ compiler to let stack unwinding 'pass through'. It seems it's not as simple as it could to make the build system understand that. Regards, Stefan