<SNIP> Hello George
> MSVC is not affected, since the code in question is only used on unix. > > With the attached patch I am now able to compile with gcc 3.2 and 3.3. I > don't understand why it does not work without. Due to the changed C++ ABI > from gcc 3.4 on I could not run the resulting binaries, You need to set your LD_LIBRARY_PATH to point to the libstdc++.so that was build with the compiler you used. Then it should run just fine. > but compilation > works, so I see no reason why it should not work on a native gcc 3.2 or > 3.3 system. The final linking fails with gcc 3.3, but that is almost > certainly another manifestation of the changed ABI. > > I will be away now, so please put this in if it is OK. > > > Georg > As a side node: Some C++ code I am working does not compile with gcc 4.0.1 on MacOSX if the includes are in the namespace, while gcc 4.0.0 on MacOSX compiles that code just fine. So moving the includes out of the namepace lyx isn't probably a bad idea. Cheers, Michael
