-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incompatible with armv7l #67
Comments
Funny, it looks like this error is actually in ruby code where it's trying to load the serialized binary. |
It would be interesting to see if you can reproduce this in isolation by capturing the data passed into |
Hm, I don't know, if I've done it right, but I've captured the data of
You can find the file here. |
Well, it looks like it's valid, insofar as it starts with
Maybe it's a ruby bug? 2.3.4 is pretty modern, but armv7l is a somewhat fringe architecture. |
I've reported this on their bugtracker :) |
Hello @mrohnstock, seeing as you're using ALARM, you should recognize me. I wanted to drop a line and let everyone on this ticket know that this is not strictly an Arch Linux ARM issue, but indeed a problem in Ruby itself. I work for GitLab, building the various vendor packages. I have seen this failure on Raspbian, and a few others. We (GitLab) are following the issue and looking for a workaround at this time. |
Is this still an issue? @WarheadsSE did you get any further? |
I confirmed today that this bug still occurs: Environment:
|
Confirmed today, bug still evident in Ruby 2.5.1 Environment:
Rails adds bootsnap to a new app by default as of version 5.2.0
Temporary fix for Rails >= 5.2.0edit # config/boot.rb
require 'bootsnap/setup' # Speed up boot time by caching expensive operations. |
I was helping a coworker debug issues around this earlier today. @fig's recommendation helped, but we also needed to disable spring using the |
Confirmed issue remains with Ruby 2.5.1 This is the dmesg after crash.
|
Is it still a problem in more recent rubies? Anyway, this is definitely not a bootsnap issue and is rather stale anyway, so I'm going to close. |
It is funny, because at the Ruby bug-tracker they are thinking it is a bootsnap issue: https://bugs.ruby-lang.org/issues/14789 Also I wonder how much this efforts will help with the ARM issues: https://bugs.ruby-lang.org/issues/15903 |
I just installed bootsnap v1.4.4 and Rails 5.2.3 on a Ruby 2.6.3 Docker image and had no trouble setting up a simple Rails app!
|
@stanhu Thank you for checking in / your feedback, very helpful! |
I ran into this when migrating an app to a Raspberry Pi 3. I'm running Rails 5.1.7 and Ruby 2.5.7. Disabling |
I think this is still related to #65 I'm trying to use v1.1.1 of this library - which indeed compiles fine on my armv7l (ODROID XU3-Lite using Arch Linux).
On using this library the following error appears:
The text was updated successfully, but these errors were encountered: