Do not build precompiled gems for Linux

[glebm]

We can't target a particular libc with RubyGems and many users aren't aware of this (#141).

[llopez]

I am having an issue related to this.

gem install sassc -v '2.2.0' --source 'https://rubygems.org/'
Building native extensions. This could take a while...
ERROR: Error installing sassc:
ERROR: Failed to build gem native extension.

current directory: /home/luigi/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/sassc-2.2.0/ext
/home/luigi/.rbenv/versions/2.6.6/bin/ruby -I /home/luigi/.rbenv/versions/2.6.6/lib/ruby/site_ruby/2.6.0 -r ./siteconf20201022-1892-zrsje0.rb extconf.rb
creating Makefile

current directory: /home/luigi/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/sassc-2.2.0/ext
make "DESTDIR=" clean

current directory: /home/luigi/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/sassc-2.2.0/ext
make "DESTDIR="
compiling ./libsass/src/memory/SharedPtr.cpp
make: g++: Command not found
make: *** [Makefile:237: SharedPtr.o] Error 127

make failed, exit code 2

I am not sure what is going on.

[januszm]

Apologies for reviving this thread, but I have basically one question: is it enough to undo this change to avoid libsass compilation when installing on Linux? So, is restoring:

ext.cross_platform = %w[x86-mingw32 x64-mingw32 x86-linux x86_64-linux]

enough to avoid time-consuming compilation? Since the sassc-ruby project looks dead and the current Ruby on Rails version doesn't use dart-sass yet, I'm going to fork and continue to use my own version of this gem. At the moment, 2 minutes of compiling sassc-ruby in environments that do not use cache is very problematic.

Another idea is to prepare a separate release of the gem called sassc-binary (or similar) with the annotation 'use at your own risk' for use in projects operating on typical and compatible systems.