On Thu, 2026-05-07 at 17:00 +0200, Robert Großkopf wrote:
Hi Harvey,
The /lib64/ld-linux-x86-64.so.2 --help command shows that /glibc-
hwcaps
contains subfolders for x86-64-v4, x86-64-v3, x86-64-v2.
Here the output ends with
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
Do you miss any entry like the (supported, searched) above?
Here is 6 × Intel® Core™ i5-8500T CPU @ 2.10GHz working with OpenSUSE
15.6
Regards
Robert
--
Homepage: https://www.familiegrosskopf.de/robert
Hi Robert,
Yes, my output ends similarly, but there are no entries like the
'(supported, searched)' against any of the 3 versions.
Does that mean I have a v1 processor and the support for v1 has been
removed with LO 26.2 onward?
....hmm, not very environmentally friendly if I have to throw my old
working configurations onto the rubbish tip. Hoping that is not yet
necessary, before I also have to leave the scene. My Dell desktop is
proving to be very robust.
Regards
Harvey
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- Re: [libreoffice-users] Failure to connect LOBase client to Mariadb host server (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.