なつき

> the error I mentioned above only happened once, and my Sass can compile CSS normally. The error means the dart-sass compiler somehow crashed unexpectedly. If it only happened once...

As a workaround, uninstalling the prebuilt gem and reinstall platform ruby to build from source fixes the issue: ``` / # gem uninstall google-protobuf Successfully uninstalled google-protobuf-4.26.1-aarch64-linux / # apk...

There are a few options here: 1. Do not ship `aarch64-linux` gem, and let both `aarch64-linux-gnu` and `aarch64-linux-musl` platforms fallback to platform ruby and compile from source. 2. Ship the...

As said early, even if we don't "officially" support linux-musl, we can avoid it from breaking out of box. - Just ship the gem with label `-linux-gnu` instead of `-linux`...

This issue used to be aarch64-linux-musl only. However, with 4.29.3 release, that `x86_64-linux` prebuilt now triggers `Segmentation fault` on `x86_64-linux-musl`: - `google-protobuf 4.29.2 (x86_64-linux)` worked on musl: https://github.com/sass-contrib/sass-embedded-host-ruby/actions/runs/12606460485/job/35136617853 - `google-protobuf...

The statistics from my own gem that has 10M+ total download shows that roughly 10% of x86_64-linux are from linux-musl, which is definitely not a small number. E.g. As of...

I was probably the earliest adaptor of splitting `linux-gnu` and `linux-musl` prebuilt, as I introduced it way before `rake-compiler` added support, using my own custom cross-platform build scripts. I have...

@dazuma In fact shipping separate `-gnu` and `-musl` does not require dropping Ruby 3.0. The way it works is that you can set different ruby version and rubygems version requirements...

Yes, I agree not able to use prebuilt is a “regression”. However, I’d argue it’s way better than segmentation fault on musl-libc, especially that 4.29.3 literally just regressed with segmentation...

@dazuma April is coming soon. Can we formally put this on the roadmap of next v31 release?