Re: Fwd: Application crashes with bootstrapping exception built on libreoffice-6-3-2 branch

Hello,

I have just tried it out with master branch. As before I have compiled it
for aarch64 (arm64-v8a).
As like with libreoffice-6-3-2 branch some fixes were required to compile
it:

1. Fixing nss error: "checking host system type... Invalid configuration
`aarch64-unknown-linux-android': machine `aarch64-unknown-linux' not
recognized"
cp config.guess
workdir_for_build/UnpackedTarball/nss/nspr/build/autoconf/config.guess
cp config.guess workdir/UnpackedTarball/nss/nspr/build/autoconf/config.guess
cp config.sub
workdir_for_build/UnpackedTarball/nss/nspr/build/autoconf/config.sub
cp config.sub workdir/UnpackedTarball/nss/nspr/build/autoconf/config.sub

2. Missing types when compiling bridge.
I copied share.hxx file from gcc3_linux_x86-64 directory and included in
two files (uno2cpp.cxx and abi.cxx) #include "share.hxx"

3. nss again:
added directive #define NS_PTR_GT_32 in:
./workdir_for_build/UnpackedTarball/nss/nss/lib/freebl/drbg.c
./workdir/UnpackedTarball/nss/nss/lib/freebl/drbg.c

4. Neon errors when compiling libpng like this:
error: undefined reference to 'png_riffle_palette_neon'
error: undefined reference to 'png_do_expand_palette_rgba8_neon'
undefined reference to 'png_init_filter_functions_neon'
../Bootstrap/Makefile.shared:60: recipe for target
'obj/local/arm64-v8a/liblo-native-code.so' failed
make[2]: *** [obj/local/arm64-v8a/liblo-native-code.so] Error 1

So, I disabled neon optimisations:
Changing the line number 130 in pngpriv.h form
define PNG_ARM_NEON_OPT 2
to
define PNG_ARM_NEON_OPT 0.

Then I have got an apk and when I am trying to open a document the crash
happens. The first time I try it libreoffice shows loader for a long time
and then crashes, after that when opening a documents it crashes almost
immediately.

I have created a bug-report here
https://bugs.documentfoundation.org/show_bug.cgi?id=127781

Is there any plans to make libreoffice working on aarch64 ? Because Google
Play now requires that all apps have also 64-bit versions of used native
libraries.

пт, 27 сент. 2019 г. в 13:44, Christian Lohmaier <lohmaier@googlemail.com>:

> Hi *,
>
> On Fri, Sep 27, 2019 at 11:58 AM Jan Holesovsky <kendy@collabora.com>
> wrote:
> > TheIstere . píše v Pá 27. 09. 2019 v 12:09 +0300:
> >
> > > If you can, please try to help with more complex
> > > issue https://bugs.documentfoundation.org/show_bug.cgi?id=127781
> >
> > Please switch to master as Miklos suggested, the branch is not 64bit
> > ready; I think Cloph has done some improvements in master recently
> > though.
>
> although only for x86_64
>
> aarch64 needs at least a patch to nss - it's configure/auto-detection
> stuff doesn't bother checking for aarch64, so resets cpu arch to arm
> otherwise, resulting in incompatible libs.
> And I guess it also will need some related fixes in bridges, similar
> to how it was done for arm (didn't look into that yet).
>
> But to also state it: There is no point in building the android
> version from a branch, it is best to use master for that. - that is
> the only branch that gets built by the only tinderbox we have for it,
> and the only branch where anything android related is done, there are
> no cherry-picks or backports to release branches for android stuff..
>
> ciao
> Christian