Stephan Bergmann <stephan.bergmann <at> sun.com> writes: > The Linux x86 OOo 1.9.x versions built by Sun contain a problematic > libgcc_s.so.1 which causes the problem you describe: If some code is > compiled with a GCC other than the exact version used inside Sun and > then run in an environment where the problematic libgcc_s.so.1 is used, > chances are high that exception handling within that code does not work.
Thanks for responding on this. I am building an Addon that I want to work for OO 2.0. > The workaround is to use the libgcc_s.so.1 that comes with your GCC, > either by replacing the file in the OOo program directory, or by using > LD_PRELOAD. I tried the approach of replacing OO's libgcc_s.so.1 by my Fedora Core 3's and it works :). Thanks for the work around. IMHO: I (or any SDK developer) should be not replacing/preloading libgcc_s. Better way might be using same settings as used in build environment. Is there any public place, where the exact build environment setup followed in sun is documented -- like usage of gcc.3.4.1 on a particular distribution. > By the way, the URE comes with a fixed libgcc_s.so.1 (and I currently > cannot remember why we do not use the fixed libgcc_s.so.1 for OOo, too, > but I will try to track that down again). I did not understand it. OOo comes with libgcc_s.so.1.1. Aditya --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
