-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Ruby 2.6.4 and Ruby 2.7.0 build failure on M1 Mac cases two test failures #97
Comments
Thank you for opening the issue! If you have time, could you run either or both |
Yes. I tried both commands on my M1 Mac, and found build failures happened. |
Additionally, did you try building Ruby with rbenv in your M1 Mac? If so, did you succeed in it? |
I could not build the both version with rbenv, either. Found the following error in the log file for 2.6.4 as well as 2.7.0:
|
Let me share y environment:
|
I'll fix it when I have a time. |
I was running into a potentially similar issue today when installing Ruby 2.5.0 on M1 with rvm.
I took it from https://stackoverflow.com/questions/65325136/problem-when-installing-ruby-2-2-9-on-mac-big-sur-m1 I hope it helps in some way. |
This worked for me with frum! |
export optflags="-Wno-error=implicit-function-declaration"
frum install 2.7.0 |
frum install 2.6.4 is also failing on m1 pro macos ventura 13.0.1 :((( |
same issue here, Mac OS Ventura 13.1, Macbook Pro with M1 Pro chip. frum install 3.1.0 |
I had the same issue as @stellorior with macOS Ventura. I was able to install by adding the
See also: https://bugs.ruby-lang.org/issues/19422 |
Summary:
Ruby 2.6.4 and Ruby 2.7.0 can not be build on M1 Mac. These build failures make the following two tests failed:
Steps reproduce:
cargo test commands::install::tests::test_install_default_version
cargo test commands::install::tests::test_install_second_version
Note: I confirmed build failure happens with rvm command
Expected result:
Pass the both test cases.
Actual result:
The both test cases fail.
The text was updated successfully, but these errors were encountered: