Charles Oliver Nutter

Interesting.

Master is a bit broken because we are trying to finish adding Ruby 2.7, 3.0, and 3.1 features. A more stable HEAD would be jruby-9.3, or just use the release....

I just ran `bundle exec rake spec` against JRuby 9.3 HEAD and there appear to be no failures: ``` Finished in 24.12 seconds (files took 9.95 seconds to load) 2139...

No worries, it's helpful for us to know that there are failures on any branch of JRuby.

@ioquatix Nothing comes to mind, but Windows pipes are a little weird at times. If we can get a reproduction with `-Xbacktrace.style=full` passed to JRuby I can look into it...

This may be the same issue as #182 but I'm not sure.

Does the sassc gem build on CRuby on M1? This would be in the makefile for libsass so I'm not sure what we can fix on our end...

Could be a bug in our mkmf that is providing the wrong flag for arch.

Show me `jruby -v` just so I can be sure you are running natively on M1. ARCH_FLAG seems like the culprit... we will need to figure out where that is...

Hmm oddly enough, JRuby appears to hardcode `ARCH_FLAGS` to `-m64` on a 64-bit platform so need to do more digging to figure out why our flags don't match CRuby.