Clojurians Log v2
babashka-sci-dev
@rahul080327 for building aarch64 we use {:machine {:image "ubuntu-2004:202111-01"}} but this image is not available anymore. We used this image because it had the right minimum glibc version (2.31).
so we need to either
• use a different machine image that still has glibc 2.31
• accept a slightly higher glibc version in a different image which means you can't run bb on older environments
thinking about this a bit more, since we favour the musl static bin more, made it the default for install.sh in all linuxes, do we phase out the dynamic bin? Do we know the usage for it?
we dont care about glibc anymore then
this is about the aarch64 binary which doesn't support musl
ah yes, makes sense. yeah will think if/when it does
> yeah will think if/when it does ?
if the aarch64 starts supporting musl someday, we can think of removing the glibc ones
yeah. another concern people sometimes have with a static binary is that they can't upgrade things that are deemed unsafe, but I guess we'll think about it when the day comes that aarch64 supports musl (in graalvm) which may take a long time
as long as things just run, I don't have a reason to remove them
yeah for me dropping some build infra is also nice
hehe, https://github.com/babashka/babashka/commits/master/.circleci
You can see the failure here: https://app.circleci.com/pipelines/github/babashka/babashka/7239/workflows/40901d24-3e9f-4bf1-9c1d-60c58ae4e4e2/jobs/39391
Any recommendations?
I’m away from the computer for a while, this image is something built by circle right? Is it possible to use an older lein image from the docker repos? The ones that are marked “official”
"ubuntu-2004:2024.05.1" works
That has a newer glibc?
does it?
no it passes the check
note that it's still 2004
but with a tag from 2024
Right, I have limited computing access now can’t check. If it passes the glibc check we should be good