Installer doesn't work on linux systems with libc other than glibc
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux, shell
- Domain
- operating-systems, release
Research direction
Start by reproducing the installer command sh CQ-editor-master-Linux-x86_64.sh on a musl-based system and inspect the extracted _conda binary with ldd. Done means the Linux installer can run without glibc-specific libc symbols, including on the reported Void Linux environment.
Written by the indexing model from the issue text.
Description
$ sh CQ-editor-master-Linux-x86_64.sh
...
Unpacking payload ...
CQ-editor-master-Linux-x86_64.sh: 493: /home/murray/cq-editor/_conda: not found
The "not found" here is referring to the libc which it is trying to load.
$ ldd /home/murray/cq-editor/_conda
/lib64/ld-linux-x86-64.so.2 (0x7f3b3ebd6000)
libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7f3b3ebd6000)
libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7f3b3ebd6000)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f3b3ebd6000)
Error relocating /home/murray/cq-editor/_conda: __snprintf_chk: symbol not found
Error relocating /home/murray/cq-editor/_conda: __realpath_chk: symbol not found
Error relocating /home/murray/cq-editor/_conda: __strdup: symbol not found
Error relocating /home/murray/cq-editor/_conda: __vsnprintf_chk: symbol not found
Error relocating /home/murray/cq-editor/_conda: __fread_chk: symbol not found
I am on void-linux with musl libc
One way to fix this issue is to compile binaries that are intended to be portable across linux distributions statically so that the only needed ABI at runtime is the linux kernel. Incidentally musl is a good option for this because it is much smaller than glibc.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 210
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CadQuery/CQ-editor
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Crash on renderOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in CadQuery/CQ-editor
Similar issues
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/semantic-kernel#14590 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
pinterest/pymemcache#662 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 62/100
gnocchixyz/gnocchi#1527 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
tenstorrent/tt-model-manager#181 ·
Maintainers usually reply within 1 day