Leap 15.5 uses glibc 2.31. I have a binary SDK from a LiDAR sensor supplier that seems to have been linked with glibc 2.34. So when I try to link with it on a Leap 15.5 system, I get: ./libscanifc-mt.so: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./libscanifc-mt.so) ./libscanifc-mt.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./libscanifc-mt.so) I am trying to see if the supplier has a version of their SDK linked with an older glibc. I hope one that is not older (in their SDK versions) than the one I have for 2.34 (which they claim is built with gcc 11). That one works fine on Tumbleweed. So I caught this when trying to do a build of our software for a different target platform (Leap 15.5). While I wait for that info, I am exploring my options. I know that glibc is a fragile and key component, so mucking about with it is generally to be avoided. Having said that, is it possible to update glibc on Leap 15.5? If so, how obtrusive is that update? As it should provide the earlier glibc interfaces as well, maybe it is rather self-contained? Just the glibc needs to be updated? These glibc things are installed in the Leap 15.5 system: glibc-locale-base-2.31-150300.58.1.x86_64 glibc-locale-2.31-150300.58.1.x86_64 linux-glibc-devel-5.14-150500.12.3.2.x86_64 glibc-2.31-150300.58.1.x86_64 glibc-devel-2.31-150300.58.1.x86_64 -- Roger Oberholtzer
On 11.10.2023 14:19, Roger Oberholtzer wrote:
avoided. Having said that, is it possible to update glibc on Leap 15.5?
Of course it is possible. Every new Leap release updates glibc. Your actual question probably is - did someone build newer glibc version for Leap 15.5. I do not know.
I am exploring my options
Build container with release that works.
On Fri, Oct 13, 2023 at 8:23 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On 11.10.2023 14:19, Roger Oberholtzer wrote:
avoided. Having said that, is it possible to update glibc on Leap 15.5?
Of course it is possible. Every new Leap release updates glibc. Your actual question probably is - did someone build newer glibc version for Leap 15.5. I do not know.
Do you mean when you go from Leap 15 to 16 it is updated? It looks to me that Leap 15.3, 15.4 and 15.5 are all using glibc 2.31. That's quite a few years at the same release. But I guess that is how Leap has been since it is more closely using SUSE components. As to if I could update glibc: the question is perhaps more if I could update glibc and not have to recompile everything. Don't newer versions of glibc support older versions at the ABI level? So that 2.34 would contain the things expected by things compiled/linked with 2.31? -- Roger Oberholtzer
participants (2)
-
Andrei Borzenkov -
Roger Oberholtzer