Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ripper issues in High Sierra (Apple changed system ruby from 1.8 to 2.3) #16

Open
amirrajan opened this issue Jan 25, 2018 · 4 comments
Open

Ripper issues in High Sierra (Apple changed system ruby from 1.8 to 2.3) #16

amirrajan opened this issue Jan 25, 2018 · 4 comments

Comments

@amirrajan
Copy link

Looks like the ruby that ships with High Sierra is 2.3.1 now as opposed to 1.8. It looks like there were some major changes to ripper in 2.3.1 that's making motion-support compilation fail. Any ideas? I can help fix it, just need to be pointed in the right direction.
@amirrajan
Copy link
Author

Looks like it's effecting motion-support and formotion.

@hboon
Copy link

hboon commented Jan 27, 2018

I'm using Ruby 2.3.1 via RVM for RubyMotion, but on macOS 10.12.6. Is there an easy way to reproduce the issue?

@amirrajan
Copy link
Author

... have two laptops T_T

Looking for a way to reproduce the issue on Sierra.

@amirrajan amirrajan mentioned this issue Feb 1, 2018
Open
@amirrajan
Copy link
Author

Related: rubymotion-community/motion-support#38 (comment)

We may not need motion_require anymore?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hboon @amirrajan