Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 788949 - app-office/libreoffice-7.1.3.2 fails to compile with gcc-11.1.0 (assembler error)
Summary: app-office/libreoffice-7.1.3.2 fails to compile with gcc-11.1.0 (assembler er...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-08 16:00 UTC by Adrian Bassett
Modified: 2021-05-08 17:34 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Bassett 2021-05-08 16:00:50 UTC
As per summary, app-office/libreoffice-7.1.3.2 fails to compile with gcc-11.1.0 on ~amd64 (-march=core2), (see below for USE flags and {C,LD}FLAGS).

The system (~2400 packages) has been almost entirely rebuilt with gcc-11.1.0.  Excluded are known-failing packages as per the gcc-11 tracker bug, those explicitly invoking clang, or for packages for which a particular gcc version is irrelevant (such as other versions of gcc itself).  Libreoffice is the only problem build...

The error thrown relates to the .../bridges/source/cpp_uno/gcc3_linux_x86-64/callvirtualmethod.cxx file, line 109: 

'"movq    (%%rax), %%rdi\n\t"'

which causes the compile to fail with the diagnostic output: 'Assembler messages:' 'Error: junk `80' after expression':

[CXX] bridges/source/cpp_uno/shared/component.cxx
/usr/portage/tmpdir/portage/app-office/libreoffice-7.1.3.2/work/libreoffice-7.1.3.2/bridges/source/cpp_uno/gcc3_linux_x86-64/callvirtualmethod.cxx: Assembler messages:
/usr/portage/tmpdir/portage/app-office/libreoffice-7.1.3.2/work/libreoffice-7.1.3.2/bridges/source/cpp_uno/gcc3_linux_x86-64/callvirtualmethod.cxx:109: Error: junk `80' after expression

I assume this is exposing a bug in the assembler routines in gcc-11.1.0, rather than being a libreoffice bug per se, as gcc-10.3.0 was not tripped up by this file (compile not yet completed with latter compiler version - seven-hour job on an Intel Core 2 - but well past the problem file).

[ebuild     U  ] app-office/libreoffice-7.1.3.2::gentoo [7.1.2.2::gentoo] USE="cups dbus gstreamer gtk java mariadb -accessibility -base -bluetooth -branding -clang -coinmp -custom-cflags -debug -eds -firebird -googledrive -kde -ldap -odk -pdfimport -postgres -test -vulkan" LIBREOFFICE_EXTENSIONS="nlpsolver scripting-beanshell scripting-javascript wiki-publisher" PYTHON_SINGLE_TARGET="python3_9* -python3_7 -python3_8*" 0 KiB

*   Used CFLAGS:    -march=core2 -mstackrealign -frecord-gcc-switches -fuse-ld=gold -O2 -pipe -Wno-expansion-to-defined -Wno-error=unused
 *   Used LDFLAGS:   -march=core2 -mstackrealign -frecord-gcc-switches -fuse-ld=gold -O2 -pipe -Wno-expansion-to-defined -Wno-error=unused -Wl,-O1 -Wl,--as-needed -Wl,--as-needed

(Incidentally, despite invoking my usual gcc-version-specific .env file to prefer gcc-10.3.0 over the system default 11.1.0 I found that the former was being ignored in favour of the the latter, and that it was only by making gcc-10.3.0 the temporary default system compiler (gcc-config) that the build would proceed.  Is the libreoffice build known to ignore a modified portage environment?)
 
Thanks.

Reproducible: Always
Comment 1 Jonas Stein gentoo-dev 2021-05-08 17:34:02 UTC
Thank you for the report. We need to have all information at hand before ticket assignment. That is why I ask you to 
* attach the logs and 
* paste the emerge info 
as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket

Please reopen this ticket (Status:UNCONFIRMED) afterwards.