Congratulations Erlang/OTP team, this is an amazing release!

@dimitarvp, it worked when building from source for me. So I wonder if this is an issue with kerl?

Next week!

Highlight blog post: Erlang/OTP 24 Highlights – A Blog from the Erlang/OTP team – The Erlang/OTP team at Ericsson, the implementors and maintainers of Erlang/OTP.

I can confirm the build works flawlessly, without any of these hacks if you use version 2.69 of autoconf, on MacOs BigSur, both intel and M1. This is also the preferred way proposed by the erlang team.
To install the downgraded version you can use

brew install cjntaylor/personal/autoconf@2.69
brew unlink autoconf
brew link autoconf@2.69
asdf install erlang 24.0

The prompt that you see means that the JIT is not able to use the native stack and stack pointer for Erlang processes. That will slightly reduce performance and perfwill not be able to show any information about Erlang functions. You will still get most of performance improvements of the JIT compared to not using the JIT.

The reason that the native stack is not used is that Alpine uses the musl C library which don’t support safely switching stacks when handling signals.

If you really need the native-stack support in Docker, it should work if you use another Linux distribution that uses glibc, for example Ubuntu.