j-pee
Thank you, ProwlerGr,
[…]
antiX (currently) gets libre-office from Debian (or debian-backports if you like), so I guess you would need to ask that question to the debian LibreOffice maintainers debian-openoffice@lists.debian.org
I will
[…]
I don’t know if that requirement can be overriden on a custom build with a compilation switch at build time (from source), and importantly if this switch would significantly impact LibreOffice new features & performance.
I’ve found this article:
https://lindevs.com/compile-for-specific-x86-64-microarchitecture-level-using-gcc-or-g-compiler
It seems this is just an option…
@ sybok
AppImages are still available, although it’s hard to find them…
https://www.libreoffice.org/download-other/
from here -> https://appimages.libreitalia.org/
Checking the v-level of the CPUs is not good enough..
Cause once you have an appimage, you can see it for yourself…
start it from the command line, and it will trow you this error:
the //something// level of your CPU is not high enough ..
What would be good would be a list of CPUs … with the v-level data…
@ Xunzi_23
Well, absolutely!
Such machines go now to the dumpster that could have worked on happily for another decade…
I mean, CPUs that were not dumped at the 32-> 64bit extermination…
It is hard not to sense a commercial interest behind this..
Libreoffice is an application that every Linux machine has… plus many more…
setting up this “CPU screening” will take down hundreds of millions of machines globally…
Sustainability with capitalism? Nonsense.
(Buy a bicycle — that has a built in motor but is still called bicycle..
it is “deleting” by overwriting, filling the space up with something else.)