Re: 回复：回复：回复：libreoffice-7.3.2 compile in arm system

[Michael Weghorn]

Do I correctly understand the discussion so far that there are 2 
different issues that you are encountering on aarch64? (This thread 
jumps back and forth between the two a bit):

1) building LibreOffice 7.3 fails on aarch64
2) building LibreOffice 7.0 works, but installation of RPM packages fails

On 25/03/2022 10.41, gcxyw1314 wrote:
> 
> [root at 1 rpm2]# `rpm -q --provides
>> ^CbXinerama-1.1.3-2.1.el7.aarch64 
> [root at 1 rpm2]# rpm -q --provides libXinerama-1.1.3-2.1.el7.aarch64
> libXinerama = 1.1.3-2.1.el7
> libXinerama(aarch-64) = 1.1.3-2.1.el7
> libXinerama.so.1()(64bit)

Thanks, that shows that the package actually provides
"libXinerama.so.1()(64bit)" on aarch64 and change
https://gerrit.libreoffice.org/c/core/+/132094 is needed.

This should solve issue 2).
Can you confirm that the installation works if you apply the above 
change before doing your 7.0 build?

> When I built versions 7.3 and 7.1, I kept reporting
> 
> /home/logsaas/libreoffice-7-1/workdir/CxxObject/xmloff/source/core/xmlimp. o: In function `SvXMLImport::SetAutoStyles(SvXMLStylesContext*)':
> 
> xmlimp. cxx:(.text+0x8b90): undefined reference to `non-virtual thunk to cppu::WeakImplHelper::acquire()'

Now we're at issue 1). Some questions to try to narrow the issue down:

Can you please try whether the same happens with the current git master 
branch instead of 7.3 (run "make distclean" first after switching 
branches), and if so, submit a more detailed error output to 
paste.debian.net, with the expiration date set to "never"?

What does your autogen.input look like? Or if you're not using that, 
what options are you passing to `./autogen.sh`?

This is on CentOS 7.7, aarch64 architecture, right?
Can you share the file `config.log` from your build directory?

> But I am https://bug-attachments.documentfoundation.org/attachment.cgi?id=172646 No modification method was found above, so I compiled on 7.06 and didn't encounter this error,

Where does that patch come from? Is there a related Bugzilla issue it is 
attached to?