Hi, after a world update, and the switch to python 3.11, none of the LibreOffice Apps start anymore... When I launch them, they load the oosplash executale but nothing appears on the screen and the oosplash process never ends. I tryed both the currently stable and the ~amd64 packages but nothing changes... Iade Reproducible: Always Selected USE flags base bluetooth branding clang coinmp cups dbus eds firebird googledrive gstreamer gtk java ldap mariadb pdfimport postgres vulkan -accessibility -custom-cflags -debug -kde -odk -test -valgrind LIBREOFFICE_EXTENSIONS="nlpsolver scripting-beanshell scripting-javascript wiki-publisher" PYTHON_SINGLE_TARGET="python3_11 -python3_10")
Created attachment 863359 [details] emerge --info
No problem here, so your first step would be to checkout what your world update did consist of.
Also, do *not* use -w in *FLAGS. It's a terrible idea and it'll confuse configure tests.
Grabbing us emerge --info for libreoffice and also its build log would help too.
(In reply to Sam James from comment #4) > Grabbing us emerge --info for libreoffice and also its build log would help > too. Hi, the emerge --info is yet in the attachments. I do not have the build.log because the package builds fine, so I lost it. Iade
(In reply to Sam James from comment #3) > Also, do *not* use -w in *FLAGS. It's a terrible idea and it'll confuse > configure tests. Ok, I will do it, but... is there a "pious soul" who can me explain how to avoid the -w in *FLAGS because this is the second time that someone ask me to do this, but no one told me how to do it in the past... help! Iade
I'm asking for emerge --info app-office/libreoffice which is slightly different and contains extra information at the bottom. Also, you're setting -w? fgrep -rsin -- "-w" /etc/portage.
(In reply to Sam James from comment #7) > I'm asking for emerge --info app-office/libreoffice which is slightly > different and contains extra information at the bottom. > > Also, you're setting -w? fgrep -rsin -- "-w" /etc/portage. Do you mean the -w option in CFLAGS environment variable? Thanks, Iade
Created attachment 863889 [details] emerge --info app-office/libreoffice I removed the -w switch from any file in /etc/portage file with the CFLAGS variable
(In reply to Sam James from comment #7) > I'm asking for emerge --info app-office/libreoffice which is slightly > different and contains extra information at the bottom. > > Also, you're setting -w? fgrep -rsin -- "-w" /etc/portage. Ok, I removed any -w switch from *FLAGS in the files of my /etc/portage folder. After performing a new world upgrade, I re-emerged libreoffice 7.5.4.2 from scratch, but nothing changes... it builds and installs fine, but when I launch it nothing appears on my GNOME desktop and the oosplash process appears to be running and consuming CPU but it does not end. Iade
The issue is not the recently-stabilized LLVM 16. I just tried rebuilding LibreOffice with LLVM 15 (and the LLVM 16 packages masked) and that didn't help.
(In reply to Brian Wong from comment #11) > The issue is not the recently-stabilized LLVM 16. I just tried rebuilding > LibreOffice with LLVM 15 (and the LLVM 16 packages masked) and that didn't > help. Yes, when I wrote yesterday LibreOffice was build using LLVM 15, and today I built it using LLVM 16, but nothing changes... Iade
(In reply to Iade Gesso from comment #12) > (In reply to Brian Wong from comment #11) > > The issue is not the recently-stabilized LLVM 16. I just tried rebuilding > > LibreOffice with LLVM 15 (and the LLVM 16 packages masked) and that didn't > > help. > > Yes, when I wrote yesterday LibreOffice was build using LLVM 15, and today I > built it using LLVM 16, but nothing changes... > > > Iade UPDATE: I built libreoffice 7.5.3.2 using gcc 11.3.0 but nothing changed... I will enable debug symbols and try again. Iade
A report on IRC mentioned disabling LTO helped.
(In reply to Sam James from comment #14) > A report on IRC mentioned disabling LTO helped. Ok, I disabled LTO and I performed a clean rebuild: 1. Unmerged libreoffice 2. Purged my local config from my home (but I already did this before opening the bug, without any sort of result) 3. Re-emerged libreoffice with debug synmbols and using clang... Now it loads correctly! Finally, I re-emerged libreoffice without debug symbols and it still works. Thanks, Iade
I've posted a bug report on the LibreOffice Bugzilla, https://bugs.documentfoundation.org/show_bug.cgi?id=156076 Let's see if it gets us somewhere.
Confirming that the bug doesn't occur when building with -clang, so it seems to be clang+lto related.
I can confirm the issue persists in 7.5.5.2 (clang/llvm/libcxx profile with -O2 -march=native -pipe -flto -Werror=odr -Werror=strict-aliasing flags system-wide).
This seems like an appropriate place to use `filter-lto`.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b45e1bd93fc1000237d1d1594e31a4bc77c8883a commit b45e1bd93fc1000237d1d1594e31a4bc77c8883a Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2023-11-29 21:19:58 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2023-11-29 21:21:37 +0000 app-office/libreoffice: filter-lto with USE=clang Bug: https://bugs.gentoo.org/907905 Signed-off-by: Matt Turner <mattst88@gentoo.org> app-office/libreoffice/libreoffice-7.5.6.2.ebuild | 3 +++ app-office/libreoffice/libreoffice-7.5.8.2-r2.ebuild | 3 +++ app-office/libreoffice/libreoffice-7.5.8.2.ebuild | 3 +++ app-office/libreoffice/libreoffice-9999.ebuild | 3 +++ 4 files changed, 12 insertions(+)
I suggested yesterday that we do this unconditionally as it usually indicates UB, but it feels a bit messy with USE=lto being used for LO right now and maybe it's okay for now.
