On 12/8/25 18:45, Peter Geerds wrote:
Hallo,
I#m testing libreofficedev26.8 with openSUSE 15.6.
My CPU:
Architecture:                x86_64
   CPU op-mode(s):            32-bit, 64-bit
   Address sizes:             48 bits physical, 48 bits virtual
   Byte Order:                Little Endian
CPU(s):                      4
   On-line CPU(s) list:       0-3
Vendor ID:                   AuthenticAMD
   Model name:                AMD Athlon(tm) II X4 635 Processor
     CPU family:              16
     Model:                   5
     Thread(s) per core:      1
     Core(s) per socket:      4
     Socket(s):               1
     Stepping:                3
     CPU(s) scaling MHz:      64%
     CPU max MHz:             2900.0000
     CPU min MHz:             800.0000
     BogoMIPS:                5825.99
     Flags:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr 
pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt 
pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid 
extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy 
abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt 
lbrv svm_lock nrip_save tsa_sq_no tsa_l1_no

libreofficedev26.8 doesn't start:

/opt/libreofficedev26.8/program/oosplash: CPU ISA level is lower than required
I suspect SSE3 is missing.

Is this a bug or does LibreOffice not support older CPUs?

See this report for details:
https://bugs.documentfoundation.org/show_bug.cgi?id=169747

LibreOffice code itself does support CPUs at the x86-64-v1 level. However, the build toolchain in AlmaLinux 9 only supports the v2 level. This means that the nightly builds at the moment require a v2 level CPU to run. This was only discovered after the baseline was raised to AlmaLinux 9 and we haven't really had time to react or think about it much.

As Linux users get their LibreOffice from distro packages, we probably would not set up a build box for stable release builds that run on v1 CPUs. Offering separate v1 builds would also complicate the downloads web page.

Ilmari

Reply via email to