Deciding on supported glibc version(s) #89
Labels
No Label
bug
documentation
duplicate
enhancement
help wanted
invalid
maintenance
peach-lib
peach-network
peach-oled
peach-stats
peach-web
question
refactor
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: PeachCloud/peach-workspace#89
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
moid was testing the installation of
peach-web
andgo-sbot
yesterday and ran into aglibc
compatibility issue withgo-sbot
. It is possible that he also had aglibc
issue with thepeach-web
binary. The basic test went like so:install.sh
scriptlocalhost:8000
peach-web
binary on the installation machine: GUI appearsBoth the
peach-web
andgo-sbot
x86_64 binaries were compiled on my development machine (glibc 2.35
). moid's machine (Linux Mint) is runningglibc 2.27
.I think we should decide on a minimum supported
glibc
version and then we can check for that in the installation script and throw a useful error if it's not supported.We can also document this clearly so there are no surprises.
For reference, here's a similar discussion on the rust-lang Github:
Minimum Supported glibc version #1412
It seems like compiling with cross might be the best way to do this (even though I had previously tried and failed to compile
peach-web
with it, prior to the Rouille refactor):x86_64-linux: lower glibc version requirement to 2.17 (compatible with centos 7) #501
aarch64-linux: lower glibc version requirement to 2.17 (compatible with centos 7) #528
Here is a table including all the supported targets for cross (includes
glibc
version for each target).After more failed attempts to cross-compile with
cross
(always running into linker errors involvingrand
orgetrandom
), I decided to try using a plain docker approach:Use
docker cp
to get the files out of the docker container, for example: