Bug#316951: openoffice.org2: compile errors

[Brian May <bam@debian.org>]

>>>>> "Rene" == Rene Engelhard <rene@debian.org> writes:

    Rene> Please do TEST whether it is applicable to Debian. This is
    Rene> the Debian BTS, not the Ubuntu one. i

    Rene> If it doesn't fail in Debian it's not really a problem for
    Rene> the Debian BTS (I do accept patches of course...).

The source is from Debian... The gcc-4.0 I used is also from Debian. I
added a disclaimer just in case it helped, maybe I shouldn't have
mentioned Ubuntu? It seems to have been a distraction.

I get the impression that the cause of problem #1 and #3 were due to
my confusion in java-gcj-compat being split. I believe it was split in
the Debian version of the package. I also believe that problem #2 was
due to a change gcc-4.0, this is also applicable to Debian. Hence I
would argue that the bugs are Debian specific, even when my
work-arounds did not produce a working solution.

However, if you continue to disagree, what do you think is the correct
forum for getting assistance in such cases? Ubuntu would claim that
their BTS is the wrong forum, as they would claim the source is from
Debian, and they don't support it. Upstream would make similar claims,
in fact the packaging issues have nothing to do with upstream.

openoffice.org2 takes so long to compile (read: hours), I didn't
really want to have to repeat the process on a Debian chroot. I
thought it was better that I consult an expert - the Debian packager,
and it would appear I was right - you already knew the answers.

    Rene> It uses java-gcj-compats jni.h symlink.  It should work on
    Rene> Debian but I did not test it anymnore with m108 since I
    Rene> already am at 114. And you need java-gcj-compat-dev in
    Rene> Build-Depends instead of only java-gcj-compat since
    Rene> java-gcj-compat was split.

Ok, so it was meant to compile against gcc 3.4. This confused me
because the build depends have a lot of references to packages built
from gcc-4.0 source.

If the symlink was in java-gcj-compats it didn't work, maybe the
symlink was moved to java-gcj-compat-dev?

    >> #2. Error that libjawt doesn't exist. This is because it was
    >> renamed to libgcjawt in version gcc-4.0 4.0.0ds1-9ubuntu1,
    >> which is in the Debian version.

    Rene> I am not stupid. I know what causes this, especially since I
    Rene> added that patch myself at the time gcc still has libjawt. I
    Rene> even got doko to backport the change. And newer versions
    Rene> have a configure check for this.

I thought if I added the solution here it could

a) help you identify the cause of my problem.

b) help others who encounter the same problem.

c) eliminate wasting time by you needing to get clarifications I have
since forgotten.

I apologise if I insulted you in anyway by providing too much
information.

    >> #3. Compile error:

    Rene> [ snip ]

    Rene> That's because you use 4.0. I know why I used 3.4 because
    Rene> binfilter didn't get patches to work with 4.0 at that time
    Rene> yet. This is NO FTBFS bug in the official package since you
    Rene> decided to build with a compiler known to not work with
    Rene> 1.9.108-1.

    >> ooo-build/build/src680-m108/binfilter/bf_forms/source/component/forms_Image.cxx,
    >> but no declaration of the class.

    Rene> You need forward declarations. Also already fixed.

I guess I need to decide now if it is more productive fixing m108, the
latest version in experimental or waiting for a new version to be
released.

I get the impression that version 108 in Debian experimental is old
and obsolete. Is there another place I should be looking to get the
most up-to-date package?

Thanks
-- 
Brian May <bam@debian.org>