datalevin

baibhavbista 2026-03-28T03:50:00.281149Z

Did the minimum glibc version for datalevin/dtlvnative change to be 2.35? Having issues running the new versions in a machine with glibc 2.34, where an older version was working (datalevin 0.9.21)

baibhavbista 2026-03-28T06:25:03.695389Z

oh btw the machine in question is running Amazon Linux 2023, in which a lot of things are apparently built on top of glibc 2.34 https://docs.aws.amazon.com/linux/al2023/ug/core-glibc.html

baibhavbista 2026-03-28T06:28:35.851959Z

for my usecase, I think I could build dtlvnative from source in a AL2023 instance and then use that variant Asking mostly to confirm that support for glibc < 2.34 has been dropped and I am not doing something wrong

baibhavbista 2026-03-29T07:14:34.828929Z

created the PR @huahaiy https://github.com/datalevin/dtlvnative/pull/13 thanks, and let me know what you think

🙏 1
Huahai 2026-03-29T23:52:12.842779Z

Merged. Thank you.

❤️ 1
baibhavbista 2026-03-30T02:50:12.325829Z

Awesome! Thanks 😁

baibhavbista 2026-03-28T08:01:42.949139Z

I had Claude investigate the issue and it seems to think that the issue is probably accidental: “”" -static-libgcc was meant to reduce system dependencies but actually increased the minimum glibc requirement from 2.34 to 2.35, because GCC 12's libgcc.a on Ubuntu 22.04 baked in a reference to the newer dlfind_object unwinder optimization. “”"

baibhavbista 2026-03-28T08:02:13.360189Z

Full response by Claude (image for easy read, markdown in snippet in case you prefer that)

baibhavbista 2026-03-28T08:02:30.473919Z

Huahai 2026-03-28T21:08:22.901729Z

Thank you for investigating. PR welcome.

❤️ 1