2.2.0 causes LoadError #146
Comments
|
I can confirm this issue; just by using rails_admin gem with this dependency |
|
I have a similar issue. 😭 Environment |
|
@atsushi-zto that one is different issue but same library with problems |
|
having the same issue, lead us to revert the update: openSUSE/open-build-service#8250 Backtrace: https://gist.github.com/vpereira/46ec18afdf1bbde20438c9933dbb1ec3 |
|
Doesn't break for us in production where we run Ubuntu + Passenger + Rails 5.2.3 + Ruby 2.5.1, but breaks in staging where we have Puma. What's the issue here? When to expect a fix? |
|
Also fails for me on CentOS 7 + Ruby 2.5. However unlike what was reported by OP, Jekyll 4.0 doesn't seem to require sassc 2.2.0. Just adding When installing the extension from 2.1.0, |
|
I am running Fedora 30 also and I have the same bug. But I found a workaround:
this should be enough then also for you: and later you will probably need it in your jekyll site directory too, if you have gems saved locally in |
|
I'm having the same issue on OSX 10.14.6 with ruby 2.5.6p201. |
|
Have a load issue too with ruby:2.6.2-alpine3.9 and ruby:2.6.3-alpine3.8 running in AWS and in local server (with docker) With a downgrade to |
|
@Shelvak I tried downgrading to no luck on OSX. |
|
@Shelvak weird that it works for you on Codefresh, for us it doesn't work there. What's your Dockerfile setup? What do you use? cc @piotrmankowski |
|
Ha, yeah the main problem in my case was that I could compile the assets and everything in codefresh but in the deploy the pods crashed by the For the downgrade I had to add libc6-compat, libsass libsass-dev and Here's my entire Dockerfile: |
hmdne
added a commit
to hmdne/sassc-ruby
that referenced
this issue
Sep 18, 2019
Fixes sass#146. See also opal/c_lexer#1 for some discussion on the issue.
|
Released 2.2.1. Please try it out and let me know if it helped! |
|
@bolandrm thanks for the release. At least for us it still happenning: Our docker file: |
|
Both, sassc-2.1.0 (downgrading approach) and sassc-2.2.1 continue failing on OSX 10.14.6/ruby 2.6.4p104 |
|
@ayanes what error are you seeing? |
|
same error |
|
Same error on Centos 7. |
|
Same error |
|
Same error on Ruby 2.6.4 and 2.6.3 on RedHat 7 |
blerner
pushed a commit
to blerner/bottlenose
that referenced
this issue
Sep 23, 2019
|
[BUG] Illegal instruction this option makes the binary NOT portable between different processor architectures Line 24 in 8b6f415 I expect that you have a VM workaround 2/ prebuild a portable gem or precompiled gem was originally portable Line 26 in 8b6f415 but it was removed in #145 thats why sassc 2.1.0 works for you @glebm @bolandrm |
tiagojsag
added a commit
to ClimateWatch-Vizzuality/climate-watch
that referenced
this issue
Oct 18, 2021
ghost
mentioned this issue
|
I deleted the folder |
|
What is the current recommendation for this issue? @eregon said this should be closed, but we continue to see reports of this in 2.3 and 2.4, and the issue is still open. Is there a recommended workaround? |
|
I am new to Jekyll and related software. I am attempting to create a GitHub Pages project using Jekyll. I (using Windows) have attempted to follow the instructions in Creating a GitHub Pages site with Jekyll - GitHub Docs as precisely as possible. I encountered the problem here using the jekyll new command. I was using a Git Bash window when I got this problem but the command (seemed to) work in a Windows Terminal window. I hope that is not causing a problem I am unaware of but otherwise it might be a workaround. Is this at all relevant and useful? |
|
I ran into this error while using Netlify to build, although I wasn't receiving the error locally. I solved the problem by using Netlify's "clear cache and rebuild" option. |
|
The issue is still present :( |
|
Getting error on Amazon Linux 2023. Setting to |
pvalena
added a commit
to sclorg/rails-ex
that referenced
this issue
Jan 17, 2024
pvalena
added a commit
to pvalena/rails-ex
that referenced
this issue
Jan 17, 2024
pvalena
added a commit
to sclorg/rails-ex
that referenced
this issue
Feb 12, 2024
pvalena
added a commit
to pvalena/rails-ex
that referenced
this issue
Feb 12, 2024
|
Still seeing this issue on latest version of Amazon Linux 2023 with sassc-2.4.0. |
|
This is a workaround I use on AL2023: cd vendor/bundle/ruby/3.2.0/gems/sassc-2.4.0/lib/sassc/
ln -s ../../../../extensions/x86_64-linux/3.2.0/sassc-2.4.0/sassc/libsass.so libsass.so |
|
Still an issue on Fedora 39 |
sschwarzer
added a commit
to sschwarzer/ftputil
that referenced
this issue
Mar 6, 2024
These led to a Ruby FFI bug that prevented me from running Jekyll. See also sass/sassc-ruby#146 .
|
I've found that, on Fedora 39, when running |
|
A fix for this that could be in the gem is change https://github.com/sass/sassc-ruby/blob/master/lib/sassc/native.rb#L10-L14 I can't tell exactly what is causing the issue but it feels related to rubygems/rubygems#6205 however it's rhel like systems that are affected? I didn't make a PR because there's no recent activity and it doesn't seem like it will get merged. |
tbhi
pushed a commit
to tbhi/sassc-ruby
that referenced
this issue
Jun 7, 2024
fleetsource-matt
added a commit
to fleetsource/sassc-ruby
that referenced
this issue
Jul 8, 2024
Update the paths FFI searches when loading libsass.so to include the gem extension path. Should allow use on Amazon Linux 2023. copied from sass#146 (comment)
fleetsource-matt
added a commit
to fleetsource/sassc-ruby
that referenced
this issue
Jul 8, 2024
Update the paths FFI searches when loading libsass.so to include the gem extension path. Should allow use on Amazon Linux 2023. copied from sass#146 (comment)
|
Problem still exists with 2.4.0 on Fedora 40. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Encountered an issue when attempting to use Jekyll 4.0.0 on Fedora Workstation 30. Somewhat similar to #141. Jekyll 4.0.0 seems to depend on sassc 2.2.0 and when executing
jekyll -vI observed an error message containing the following:The "fix" I found is to downgrade Jekyll to version 3.8.6 and sassc to 2.1.0, after which the error no longer appears.
The text was updated successfully, but these errors were encountered: