Hi Απόστολος,

On 04.01.2014 19:41, Απόστολος Συρόπουλος wrote:
Today I tried to investigate a little bit why uno fails, in particular why
build --all:testtools fails in OpenSolaris. So I tried to rebuild some
libraries with debugging information.

I have used build debug=true dbglevel=2 to build libuno_cppu.so.3 and
here is what I get:

Compiling: cppu/unxsogi.pro/misc/uno_cppu_version.c
Compiling: cppu/unxsogi.pro/misc/uno_purpenvhelpergcc3_version.c
Making:    libuno_cppu.so.3
### OFFSET_OF(AlignSize_Impl, dDouble) = 4 instead of expected 8!!!
/extra/sources/OpenOffice/aoo4/main/solenv/bin/checkdll.sh: line 60: 4017: 
Abort(coredump)
dmake:  Error code 1, while making '../unxsogi.pro/lib/libuno_cppu.so.3'
ERROR: error 65280 occurred while making 
/extra/sources/OpenOffice/aoo4/main/cppu/util

The following patch solves the problem:

--- cppu/source/uno/data.cxx.old    Σαβ Ιαν  4 20:13:17 2014
+++ cppu/source/uno/data.cxx    Σαβ Ιαν  4 20:13:10 2014
@@ -357,7 +357,7 @@

  #if defined(INTEL) \
      && (defined(__GNUC__) && (defined(LINUX) || defined(FREEBSD) || 
defined(OS2
)) || defined(MACOSX) \
-        || defined(__SUNPRO_CC) && defined(SOLARIS))
+        || (defined(__SUNPRO_CC) || defined(__GNUC__))  && defined(SOLARIS))
  #define MAX_ALIGNMENT_4
  #endif

Great!

As expected the source tree has zero support for Solaris and GCC (The Sun 
people did
lousy job as far it regards GCC and Solaris).

Well, building Solaris OOo with GCC was as interesting to the Sun people as Microsoft is in building their MSO with the Sunpro or the GCC compiler: Almost zero.

Now, I rerun build --all:testtools and I get the following:
[...]
### unexpected exception content! failed
exception test failed
oneway exception test failed
exception occured: error: test failed!

Ouch! None of the exception stuff works in your new build. That is a hard nut to crack...

Can anybody help me proceed?

You already had the UNO bridges and their tests working in your older builds. Do you have an idea, what might have caused this bad regression? Getting back to the old (working) behavior is the only reasonable thing to do. Debugging/Fixing UNO bridge is not much fun and doing it remotely with only an occassional mail here and there is almost impossible.

Herbert

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to