Crystal 1.1.0 binary seems to be broken
Compiling any program with the Crystal 1.1.0 binary from the Alpine edge package fails with an invalid memory access:
$ crystal eval 'puts "Hello World"'
Invalid memory access (signal 11) at address 0x55f4a3f8182c
[0x55f463e76186] ???
[0x55f463e76153] ???
[0x7fcd8871bc4b] ???We don't experience this problem with the official binaries provided in the binary distribution tarball, so it seems to be caused by the way the binary is built for the alpine package.
This has first been reported on the Crystal forum at https://forum.crystal-lang.org/t/segmentation-fault-when-running-crystal-build/3530/2 and there is some more debug information there.
Due to lack of native aarch64 hardware, I've only been able to reproduce on x86_64 so far.
This is a serious issue and makes the package unusable.
I'm wondering how this could go unnoticed and would've expected that the check recipe to spot this kind of problem.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information