Hi, Rene.
On Thu, Jul 16, 2020 at 4:11 PM Rene Engelhard <r...@debian.org> wrote:
> Am 15.07.20 um 17:42 schrieb Rene Engelhard:
> > Am 15.07.20 um 17:34 schrieb Rene Engelhard:
> >>> ,----
> >>> | $ libreoffice
> >>> | : CommandLine Error: Option 'polly' registered more than once!
> >>> | LLVM ERROR: inconsistency in registered CommandLine options
> >>> `----
> >>
> >> I'd have a look what causes this. Wherever this "polly" "command-line"
> >> option is set.
In the context of LLVM polly is the integer polyhedral optimization
"engine" (GCC also uses something similar called graphite, if I am not
mistaken). What causes it to be included multiple times, I don't know
(but I suspect, see below).
> We should discuss there, probably. Different option but... I still
> believe it's not a LO problem but a problem of something using LLVM or
> someone configuring something (using LLVM) badly.
I tested stuff a little bit more and, now, I can tell more about this
issue. Are you ready for a journey? :-) I hope that you are.
First, I completely removed libreoffice and everything that it
recommended or suggested.
Then, I went to snapshot.debian.org and installed version 1:6.4.5-1
(only writer). It worked.
Then, installed impress. It still worked.
Then, I upgraded everything to version 1:7.0.0~rc1-5. It *STILL*
worked, to my amazement.
Then, remembering that Calc started using OpenCL (at one point or
another), I installed calc. It *STILL* worked.
I installed the gtk3 component, because the default interface is
horrendous. It still worked.
Then, I installed beignet-opencl-icd. It *STILL* worked. (I have a
notebook with an integrated intel chip and a discrete AMD card)
Then, I installed mesa-opencl-icd. It pulled in a lot of packages,
including clang-common-10-dev and other stuff. It *still* worked, to
my amazement.
Then, I decided, just for fun, to remove the directory
~/.config/libreoffice (actually, I simply renamed it to
~/.config/libreoffice.old). NOW, it didn't work and showed again the
"polly" message.
If I copy back the contents from ~/.config/libreoffice.old to
~/.config/libreoffice and invoke libreoffice, then it works again.
OK, so, mesa-opencl-icd was the thing that caused some instabilities,
right? I then, decided to remove it (and its dependencies), just
keeping Intel's beignet and, bingo:
I can fire up libreoffice with both a prepopulated
~/.config/libreoffice or not and it works without any problems.
With mesa-opencl-icd/20.1.2-1 installed, I can only run libreoffice
successfully if I have a preexisting ~/.config/libreoffice from a
previous successful run (an empty directory prevents it from running).
So, part of the mystery is unveiled (but not solved)... The problem is
definitely not with libreoffice, but with LLVM & Co.
Just for the record, the packages that were installed when
mesa-opencl-icd/20.1.2-1 were:
* lib32gcc-s1/10.1.0-4
* lib32stdc++6/10.1.0-4
* libc6-i386/2.30-8
* libclang-common-10-dev/1:10.0.1~+rc4-1
* libclc-amdgcn/0.2.0+git20190
* libclc-dev/0.2.0+git20190
* libclc-r600/0.2.0+git20190
Based on this, I guess that this bug should probably be reassigned to
the LLVM people, perhaps (or to the mesa people)...
Oh, I just took a minute and tested the following:
If I remove beignet and keep the mesa icd, the problem still persists:
If I have an empty "profile", libreoffice doesn't start (and shows the
polly message from above). If I copy a "profile" that was used
successfully in the past, then libreoffice starts with the mesa icd &
Co.
Well, that's it for the moment. I hope that this is informative.
More precise information, straces and logs are available if needed.
Thanks for taking care of libreoffice in Debian,
Rogério Brito.
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
