moving the discussion on https://github.com/babashka/babashka/pull/1445 here @thiagokokada whats the thing that breaks when those two vars are set? this just for my info 🙂
It tried to run setup-musl script with BABASHKA_ARCH set as amd64
Right and the error GraalVM only supports building static binaries on x86_64. comes from the setup-musl?
i was thinking that var messes up the call to native-image somehow?
> Right and the error GraalVM only supports building static binaries on x86_64. comes from the setup-musl? Yes
ahh i see it, been a while for me too 😅
BTW, the build error is probably some flaky test
It is not related to the bump at all
yeah we've seen it before
looks fine for me, merging it
thanks3
maybe will try a rerun on the flaky one once
thanks
From the GraalVM slack: > Yeah, so just pick an old base image and use that. This is a very old and long-standing Linux problem. It bites everyone eventually and then you learn the hacks. ~20 years ago I wrote a tool that could compile native code on newer Linux distros/glibcs whilst enabling them to run on older distros, using a variety of obscure linker/compiler features. That sort of thing never became mainstream though because Linux distros assume they're the only distributor of binaries and everything gets compiled as a unit. Closed world assumption on a bigger scale. (edited)
So I guess all graal projects should be mindful about it
Perhaps it's better to just base off debian and then install everything yourself
Still at some point we'll have the issue i guess. And on debian stable if we're updating could be quite a lot every 2 years or so