Galmes Pierre-Andre wrote:
Le Vendredi 09 Septembre 2005 15:28, Stephan Bergmann a écrit :

Galmes Pierre-Andre wrote:

Hello,


Hello Stephan,


Maybe there is something to be done for gcc4.

Yes, looks like the SDK is not yet ready for GCC 4.  Note that there are
no successful builds of OOo or SDK on GCC 4 yet, so what you are doing
is "experimental."  Anyway, please file an issue that the above will
have to be adapted for GCC 4, so that it is not forgotten.  (It seems
that GCC 4 is compatible enough with recent GCC 3 versions, so that we
can continue with a single "gcc3" for both versions.)


Ok, I will open an issue.


After, I tryed to hard code the line :
CPPUHELPERLIB=-luno_cppuhelpergcc3

I compiled, but then I suppose there are linkage problems between the two
versions. Here is the error :

$ make countermain.run
cd /tmp/oooSdk_build//OpenOffice.org2.0_SDK/LINUXexample.out/bin &&
countermain
terminate called after throwing an instance of
'com::sun::star::registry::CannotRegisterImplementationException'
/bin/sh: line 1:  8377 Abandon                 countermain

This most probably is due to the old libgcc_s.so.1 included in
(Sun-builds) of OOo (are you using a Sun-built OOo?).  Try replacing
<ooo>/program/libgcc_s.so.1 (watch out---that might be a symbolic link
to libgcc_s.so.1.1) with the one that comes with your GCC 4 (probably
found under /lib on your system).


In fact, following your instruction does not change anything to the error... I am now trying to compile GCC3.4. Hope this works !

I just tried the Makefile.pln-test from uretest.zip using the Hamburg-built (GCC 3.4.1) URE and GCC 4.0.1, and the test succeeded (the test includes exception handling). So, I am not sure what your specific problem was, but it seems that there is no inherent incompatibility when mixing GCC 3 and 4 for UNO use.

-Stephan

Thanks for the answer,
Pierre-André

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to