Ruby 2.3.1 build issues on Mac OS X El Capitan 10.11.6 #1949
Replies: 27 comments 1 reply
-
I'm getting different errors in a similar environment.
Puzzled by the references to |
Beta Was this translation helpful? Give feedback.
-
I hade the second problem described here, probably because Xcode was upgraded. Solved by running
|
Beta Was this translation helpful? Give feedback.
-
@stenlarsson nailed it. Thanks! Seems that installing Xcode on a new machine doesn't automatically install the command line tools. Could have sworn that used to be the case. Or at least they would prompt you to. |
Beta Was this translation helpful? Give feedback.
-
@pc-mreeves Might that be the cause of your problems as well? |
Beta Was this translation helpful? Give feedback.
-
It could definitely be related. However, IIRC I did not need to run that command because I ran the homebrew install first which installs the command line tools: If I try to run it again I get this: I'll update and see if that fixes the issue... (after 3.44 gigs (!!!) downloads and installs...) |
Beta Was this translation helpful? Give feedback.
-
@pc-mreeves Did the App Store download fix the problem for you? |
Beta Was this translation helpful? Give feedback.
-
Unfortunately no... As I mentioned I had manually run I can still cd to the directory and run make install and then it works. |
Beta Was this translation helpful? Give feedback.
-
@pc-mreeves Thank you for the reply! May I ask: when you say, "I can still |
Beta Was this translation helpful? Give feedback.
-
(Sorry had to edit this because 2.2.1 is failing with a different error) When the
If I cd to /var/folders/_y/qc89fk7n3m1f1p5pt8kpsgvdv009dp/T/ruby-build.20161003095011.89195 I can run |
Beta Was this translation helpful? Give feedback.
-
Confirmed -- I got the same output re: I'll also note my ruby is |
Beta Was this translation helpful? Give feedback.
-
@pc-mreeves thank you for your suggestion to |
Beta Was this translation helpful? Give feedback.
-
It seem for 2.3.1, under the working tree, there is another folder called |
Beta Was this translation helpful? Give feedback.
-
I'm getting this when make install.. JM:ruby-build.20161117072715.65539 jm$ make install |
Beta Was this translation helpful? Give feedback.
-
I got the same error when I was trying to install ruby 2.4.0 on OSX Yosemite 10.10.5, which is resolved by prefixing install command with an But why do I have to append an I think prefixing install command with |
Beta Was this translation helpful? Give feedback.
-
This is still an issue 2 years later
This makes me so sad - even with a fairly simple workaround. |
Beta Was this translation helpful? Give feedback.
-
Closing due to staleness. If there is more recent information, steps to reproduce, workarounds, please open a new issue! 🙇 |
Beta Was this translation helpful? Give feedback.
-
Our team still has this issue.
In my particular case, the machine is new install of MacOS (vs upgraded) with:
Workaround to What can we do to help troubleshoot and find resolution? |
Beta Was this translation helpful? Give feedback.
-
July 2019, this still happens.... workaround... cd into the folder of the build and |
Beta Was this translation helpful? Give feedback.
-
This is still a problem. I don't compile stuff very often so this was an all-morning struggle. To provide some specifics for others in this situation: After downloading the patches, this was the command that failed with the permission issue: error:
The file it will fail on with permissions can vary but this was my fix:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Same problem here on MacOS 10.15.1. I solved the problem doing the
After the installation completes, set the ruby version in Update 06-12-2019: SSL certificates fix After running the commands above, I was able to run
Now you should be able to see everything is fine with: Update 20-02-2020: Still happening
|
Beta Was this translation helpful? Give feedback.
-
Same issue on MacOS 11. cd into working directory and make install fixes it. |
Beta Was this translation helpful? Give feedback.
-
Dec. 2019 and still happening! |
Beta Was this translation helpful? Give feedback.
-
Finally Got it working !! |
Beta Was this translation helpful? Give feedback.
-
Same issue on Mac OS Monterey 12.2.1, and I fixed navigating to the temp folder and running |
Beta Was this translation helpful? Give feedback.
-
I was really stubborn about this. After adding debug output to ruby-build I noticed that the make command i runs to build ruby passes If you cd to the temp dir that ruby-build was using run I don't know much about make in general and even less about how make handles parallel execution. So i don't really know how i can use this difference to identify the root cause of this error. |
Beta Was this translation helpful? Give feedback.
-
I'm experiencing this issue as well on MacOS 12.5.1 with the stable version of |
Beta Was this translation helpful? Give feedback.
-
I am getting an odd error when building 2.3.1. I get one of two errors:
or
I have checked and there is nothing strange about the perms of these files. Perhaps antivirus or something like that is the culprit?
However if I cd
/var/folders/_y/qc89fk7n3m1f1p5pt8kpsgvdv009dp/T/ruby-build.20160909110514.33878/ruby-2.3.1
and runmake install
it seems to install it successfully to~/.rbenv/versions/
Any ideas or can I provide more information? Does installing ruby 2.3.1 this way cause any problems?
make test
also passed.Beta Was this translation helpful? Give feedback.
All reactions