Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

rbenv install 1.9.3-dev fails to build due to syntax error #209

Closed
conradwt opened this Issue Sep 12, 2012 · 7 comments

Comments

Projects
None yet
3 participants

I'm seeing the following error in the logs /var/folders/r7/2szvgw615tl507ndcnb89x6w0000gn/T/ruby-build.20120912081800.3373.log:

installing default ripper libraries
compiling ripper.c
parse.c:695: error: expected ‘)’ before ‘->’ token

What if you build 1.9.3-dev by hand, without using ruby-build? In other words, is this ruby-build's problem or 1.9.3-dev's problem?

@mattneub Matt, let me give that a go because there might be issues with Ruby 1.9.3 trunk and I'll get back to you.

skaes commented Sep 17, 2012

I had the same problem, even though I'm not using ruby-build. After removing the bison install from MacPorts (version 2.6.2_0) and removing the generated parse.c from the old build, everything compiled cleanly.

Are you even using OS X? The bug report doesn't mention any specific system.

I would suggest to check which bison version is in your program search path.

I'm on Lion and the bison shipped by Apple is 2.3.

@skaes Yes, I'm on Mac OS 10.8.1 and I'm also using Bison 2.6.2. Bison 2.6.2 doesn't appear to be backward compatible to Bison 2.3 or there's a bug within the Bison 2.6.2 sources. Any how, I was able to deactivate the MacPorts install of Bison and the build completes successfully now. Thanks for the information.

@conradwt That is very useful to have here in the archives, thanks for reporting back! (I don't use MacPorts so I didn't encounter the issue...)

@mattneub I have also reported this issue to the Bison maintainer for MacPorts.

@conradwt You should perhaps close this issue, as you have shown it is not an rbenv / ruby-build problem (you can see a Close button beneath the last comment).

@conradwt conradwt closed this Sep 22, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment