2.6.6 on ARM64 #1946
-
I've managed to install 2.7.2 and 3.0.0, but 2.6.6 fails with the following error
|
Beta Was this translation helpful? Give feedback.
Replies: 22 comments 4 replies
-
It's known issue. Ruby 2.6 didn't support M1 macOS yet. If you want to use Ruby 2.6 with M1 macOS, Can you file it to https://bugs.ruby-lang.org/? Thanks. |
Beta Was this translation helpful? Give feedback.
-
Thanks for pointing me in the right direction. |
Beta Was this translation helpful? Give feedback.
-
@nelseric I guess the error is only due to fiddle. Probably, you can install Ruby 2.6 with specifying |
Beta Was this translation helpful? Give feedback.
-
@mrkn Thanks, that worked |
Beta Was this translation helpful? Give feedback.
-
I was also able to install Ruby 2.6.6 with this
|
Beta Was this translation helpful? Give feedback.
-
I ended up doing this:
|
Beta Was this translation helpful? Give feedback.
-
@santostiago, that worked for me. Thank you! |
Beta Was this translation helpful? Give feedback.
-
This worked for me in My Apple M1 - Please try this if you are facing issue (I tried for ruby v 2.6.0) and don't need rosetta too Once again thanks worked with 2.6.6 |
Beta Was this translation helpful? Give feedback.
-
THIS WORKED FOR ME These 3 lines of code worked for me. Just make sure to change the version number to 2.6.2 (if that is what you need)
|
Beta Was this translation helpful? Give feedback.
-
thank you so much @santostiago 😭 this actually solved my
|
Beta Was this translation helpful? Give feedback.
-
more thanks for you @santostiago !!! you saved my day !!
endless ffi errors
|
Beta Was this translation helpful? Give feedback.
-
@jujudellago Did you try to update the ffi gem? Or uninstall and reinstall it with the same flags shown above prefixed before you run bundle install? Bundler accepts build flags configuration it can store for specific gems. See: https://bundler.io/v1.16/bundle_config.html#BUILD-OPTIONS |
Beta Was this translation helpful? Give feedback.
-
Oh, so actually my error was just related to my project, I had a hardcoded version of ffi in my gemfile To figure this out I just made an empty rails app, saw everything was fine, and realized I had the wrong ffi in gemfile.lock With other compatibility issues I ended up using ruby 2.7.2 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I’m sorry the flag is Seriously? Can we please fix that if it wasn’t a typo on your side? Seems bad. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
RVM is much more fussy on the installation process (pgp keys, openSSL installation). And after all that, The combination of I use RVM on my Intel Mac...but I'm inclined to switch to rbenv now. (My use case is simple, so I skipped the |
Beta Was this translation helpful? Give feedback.
-
@michaelsmith-st Were you able to get Ruby 2.6.6 to install via RVM in the end? I haven't had any luck so far, and pretty much every answer pointing to its installation through the use of flags and so on ends up as a [broken] install for me. |
Beta Was this translation helpful? Give feedback.
-
Just wanted to chime in and confirm that this is safe to do... I didn't really understand what this would actually do so I dug in a bit... wanted to be sure this wouldn't cause unexpected issues down the line* To cut to the chase... You can see here that by setting the USE_FFI_CLOSURE_ALLOC macro, the offending function (ffi_prep_closure) is never referenced. And to confirm that the macro makes sense (the ffi_closure_alloc function is indeed available):
*In hindsight, I guess that's what compilation is for in the first place, lol |
Beta Was this translation helpful? Give feedback.
-
encounter same problem in macbook m1
I tried this I am able to install ruby 2.6.5, not sure if this |
Beta Was this translation helpful? Give feedback.
-
Thanks for all the comments. Here is the exact commands I used to install 2.6.7 using rbenv on an M1 Pro:
I hope this multi-line version will be more readable to others. |
Beta Was this translation helpful? Give feedback.
-
This worked with chruby and 2.6.5 for me. Thanks! |
Beta Was this translation helpful? Give feedback.
Just wanted to chime in and confirm that this is safe to do... I didn't really understand what this would actually do so I dug in a bit... wanted to be sure this wouldn't cause unexpected issues down the line*
To cut to the chase...
You can see here that by setting the USE_FFI_CLOSURE_ALLOC macro, the offending function (ffi_prep_closure) is never referenced.
And to confirm that the macro makes sense (the ffi_closure_alloc function is indeed available):