Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Ubuntu 18.04] zsv linked GLIBC version issue #90

Closed
iamazeem opened this issue Dec 10, 2022 · 3 comments
Closed

[Ubuntu 18.04] zsv linked GLIBC version issue #90

iamazeem opened this issue Dec 10, 2022 · 3 comments
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request

Comments

@iamazeem
Copy link
Collaborator

zsv did not work after installing the .deb packages.

Environment:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic

Downloaded and tested with:

Error:

$ zsv version
zsv: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by zsv)
zsv: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by zsv)

Linked libraries:

$ ldd $(which zsv)
/usr/bin/zsv: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /usr/bin/zsv)
/usr/bin/zsv: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/bin/zsv)
	linux-vdso.so.1 (0x00007ffe0ffed000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd781c9a000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd781a96000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fd7816f8000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd781307000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fd781eb9000)

As these binaries are built on Ubuntu 20.04 so this issue is expected for the versions lower than 20.04 (where GLIBC version is not supported).

To support Ubuntu 18.04, the runner should be the same.
However, the Ubuntu 18.04 runner has been deprecated.

One solution could be to generate a statically linked binary to resolve this issue.
Another could be to build binaries on Docker containers and distribute those.

In addition, the minimum supported version of the target OS for the prebuilt binaries should properly be documented in the README in case the static linkage is not possible.

Thanks!

@iamazeem iamazeem added bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request labels Dec 10, 2022
@liquidaty
Copy link
Owner

Thank you. I think we should make it a static build. Could you make those changes?

@iamazeem
Copy link
Collaborator Author

Sure, I'll try to generate static builds for the supported Linux variants.

However, it might not be possible for macOS, and we'll have to resort to -mmacosx-version-min compiler flag to specify the lowest supported version e.g. -mmacosx-version-min=10.15, if it comes to that. 🤔

@iamazeem iamazeem assigned iamazeem and unassigned liquidaty Dec 13, 2022
@iamazeem
Copy link
Collaborator Author

iamazeem commented Jun 1, 2023

@liquidaty: Was this reported by any other users or experienced internally?
I was planning to work on it by building on Ubuntu 18.04 container.
But, if it's not an issue, this can simply be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants