-
Notifications
You must be signed in to change notification settings - Fork 780
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
Install 2.1.0 & 2.1.2 Fail OSX 10.9.4 #859
Comments
2.1.2 is old version. Can you try with Ruby 2.1.8? |
@hsbt Thanks, yes I did. All main ruby versions fail. But I was able to install jruby-9.0.0.0 |
@lacostenycoder I can see how the LDFLAGS error happened for Ruby 2.1.0 (fixed in 3fe1eaf), but I can't see how the identical error can happen for other Ruby versions. Can you try to install a recent Ruby version such as 2.2.4 and 2.3.0 and paste us the full build log as a Gist? Thanks |
Seems like the error isn't related to LDFLAGS:
But I don't know what's causing it. If you say that every Ruby version fails for you, perhaps this is something specific to your system. Can you check whether you installed any newer versions of system utilities such as |
@mislav agreed. I did however install gnu-sed under recommendation as I had been getting sed errors prior to that, found in first post in this thread. So here's what I've got. Most recently I reinstalled node and npm outside of homebrew and deleted my prior brew node install. I also installed mono for testing .NET dev on OSX. Finally, my problems seemed to have started after brew updating which updated my rbenv install. That's when I tried brew deleting it and just installing from the git repo. Since then it's been down the rabbit whole. Here's what I got:
|
Updating rbenv has likely nothing to do with your problem, since rbenv doesn't handle installing Ruby versions. The ruby-build plugin does, but it seems you have an up-to-date version of that. There's nothing in your brews that stands out to me as a potential culprit. Maybe you could try downloading Ruby source and running Update: seems like @Cha2d had the same error rbenv/rbenv#658 |
@mislav so I just tried running ./configure from source of ruby 2.1.8 and it seems to fails at same line. Not sure what I should be inspecting for.
|
this is the end of the config.log
|
After a day of tail chasing, the problem seems to have been simply path load order issues and/or homebrew conflicts. Finally working after deleting rbenv, killing cleaning path, and brew install rbenv. |
That's pretty bizarre, since I can't see how PATH had something to do with this, but I'm glad you solved it! Thanks for updating. |
Hello, I'm not sure if I should open a new issue for this. But I'm facing the exact same error with OS X 10.12 and ruby 2.3.1. I tried uninstalling and reinstalling both rbenv and ruby-build, to no avail. Configure seems to be changing directory somehow ... and hence is not able to find the Makefile. Any advice? Thanks.
|
I had a somewhat similar problem but unrelated to homebrew. I do use ruby for compiling stuff from source, though, e. g. with my own projects of compiling and installing programs from source (on my linux box; it's a bit similar to homebrew but not as advanced as homebrew is) For a weird reason, shell redirection happened for GNU autoconfigure based projects on my system. Which caused problems all of a sudden: I could not compile any program anymore. I could compile cmake programs and my own .c files just fine though. There were various errors, some bugs; e. g. "cc compiler can not compile executables" or something like that, which I knew was bogus since I could compile my own .c files just fine. I had exactly the same problems mentioned above too, such as "configure: error: could not make ./config.status". Creating that file via "touch config.status" worked just fine, so obviously the error must have been wrong. Checking through various config.log files, I saw wrong file descriptors being used. The message usually included "bad file descriptor", e. g. >&5 or something strange like that. I have no idea why such file descriptors are used. At any rate, I then read that $PATH may be causing an issue - and indeed, when I changed the $PATH, suddenly I could compile again! In my case, $PATH prioritizes on /System/Index/bin/ which is the $PATH used on GoboLinux by default. I have no idea why this can fail (it worked for many years for me); I assume I may have changed something... it is difficult to debug that giant mess that is bash + autogenerated shell scripts. But at any rate, putting /usr/bin/ as path there worked and I could compile again. I do not know if this has anything to do with the problems here but I got exactly the same lines of problems and even more. So as odd as it may sound, $PATH can really be an issue. I may be further investigating but right now I am just glad that I can compile again without having to re-install. The whole GNU autoconfigure toolchain is so brittle, that is actually the first time that I think that cmake beats that old chain. |
@shevegen Yep. PATH load order is often the culprit with build problems. |
Earlier I was having problems with Hombrew install so deleted everything and did clean clone of latest RBENV 1.0.0 master. Now I can't install any Rubies.
log errors from 2.1.2 (which I tried to install first with similar error above)
The text was updated successfully, but these errors were encountered: