This repository has been archived by the owner on Oct 6, 2022. It is now read-only.
Link static build against musl #36
Comments
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
@thiagokokada @ericdallo @borkdude got it to build and the tests to pass! have a look on the musl branch, let me know if it could be done better? |
lispyclouds
added a commit
that referenced
this issue
May 9, 2021
borkdude
pushed a commit
that referenced
this issue
May 9, 2021
Closed by #37 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See oracle/graal#2691 (comment)
Linking against the host glibc is a bad idea, we should link against musl for all of our static builds.
Then perhaps all the weird segmentation faults etc are over...
@lispyclouds will try to do this for pod-babashka-aws first.
/cc @thiagokokada @ericdallo @lispyclouds
The text was updated successfully, but these errors were encountered: