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

Does not build on Debian Bullseye #1641

Open
aaron-michaux opened this issue Oct 19, 2023 · 1 comment
Open

Does not build on Debian Bullseye #1641

aaron-michaux opened this issue Oct 19, 2023 · 1 comment
Labels

Comments

@aaron-michaux
Copy link

aaron-michaux commented Oct 19, 2023

Describe the bug

The script linux/appimage/build.sh has the following line:

run cp -a "$pyprefix/lib/$pyldlib"* "$pyprefix/lib/$pypy3lib" "$pydist/lib/"

This will fail on Debian Bullseye (10), because the python3 binary does not link to libpython*.so. That is, the copy command fails because the files being copied don't exist, and are not needed. This can be fixed:

run cp -a "$pyprefix/lib/$pyldlib"* "$pyprefix/lib/$pypy3lib" "$pydist/lib/" || true

To Reproduce

On Debian Bullseye

linux/appimage/build.sh --python /usr/bin/python3 --wheel dist/plover-4.0.0rc2-py3-none-any.whl

Expected behavior

The App image should build.

Operating system

  • OS: Debian Bullseye (10)
  • Plover Version: 53c416f (ie., head as of 2023-10-19)

Hardware

x86_64

@aaron-michaux
Copy link
Author

As a general note, it would be helpful if the AppImages were built against a conservative glibc... so, for example, using CentOS.

This is because, unfortunately, glibc cannot be statically linked.

Alternatively, the AppImage could be built on AlpineLinux, which is based on musl, which can be statically linked, which means that the AppImage depends only on the kernel itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant