-
Notifications
You must be signed in to change notification settings - Fork 332
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
Incompatibility with Ruby 2.2.0 #229
Comments
Not an expert in C and can't figure out why the macro expansion is not working properly. I was able to push a small fix by avoiding the use of |
Hi! I'm having the same issue |
Yup, same thing here:
|
It looks like this is the commit that changed |
Here is some discussion about how the C preprocessor deals with scanning function-like macro arguments: https://gcc.gnu.org/onlinedocs/cpp/Argument-Prescan.html#Argument-Prescan |
We(ruby-core) fixed our bundled json gems like forked. see diff https://github.com/zzak/json/compare/ruby-2.2 I think we should backport our patchs into this repository. Please wait until merge it and bump version 🙇 |
Any ETA on when a PR might be coming? e.g. days, weeks, undefined |
I'm still trying to work out a patch to fix 1.8.7, since that is the only blocker I imagine it should be soon. Unless we just drop 1.8.7 support all-together. |
I'm not that familiar with this gem's code base.... would it not be easier to add something to the backports gem (marcandre/backports) and have that 1.8.7 dependency rather than drop support? |
The problem is the capi has changed, and this struct isnt available in 1.8.7: https://github.com/zzak/json/blob/ruby-2.2/ext/json/ext/generator/generator.c#L518 |
Ack. The backport may have to be a pure ruby implementation. Rather than pull the pin (either way) maybe a non-1.8.7 gem can be released as a workaround - this will also give time to assess the level of pain caused in the 1.8.7 community. My 2c on 1.x.y: |
Same issue here |
Given ruby 1.8.7 has had its EOL announced. I think the most pragmatic approach to take is to replace it with rbx 1.3 which I've just seen is continuing 1.8.7 compatibility - but fixing bugs. |
When is a real fix available? |
I have the same issue. Browsing internet I found this file that looks interesting http://fossies.org/linux/misc/ruby-2.2.0.tar.gz/ruby-2.2.0/ext/json/fbuffer/fbuffer.h They replaced the problematic line with
|
Indeed, after applying following patch the tests pass on my Linux Arch with ruby 2.2.0 installed
|
It's not that I need json-1.7.7.gem |
Excon depends on json via the rdoc dependency. We need to add an direct dependency on json since the rdoc dependency for json (~> 1.4) doesn't enforce 1.8.2. See: ruby/json#229
Excon depends on json via the rdoc dependency. We need to add a direct dependency on json since the rdoc dependency for json (~> 1.4) doesn't enforce 1.8.2. See: ruby/json#229
Excon depends on json via the rdoc dependency. We need to add a direct dependency on json since the rdoc dependency for json (~> 1.4) doesn't enforce 1.8.2. See: ruby/json#229
Excon depends on json via the rdoc dependency. We need to add a direct dependency on json since the rdoc dependency for json (~> 1.4) doesn't enforce 1.8.2. See: ruby/json#229
I think this can be closed with the 1.8.2 release. I just tested and was able to install |
Thank you I am closing this issue. |
When installing the json gem with ruby 2.2.x, compilation fails. The details of why it is failing are in this[0] github issue. Subsequent gem releases (1.8.2+) have fixed the issue, so this commit bumps the gem to the latest non-broken version so that people with ruby 2.2.x can install and run the gh-pages for rails-erd locally. [0] - ruby/json#229
when using Ruby 2.3.1 because of a compatability problem with the JSON gem ( ruby/json#229 ). To do this I just removed the old gem lock file and generated a new one.
when using Ruby 2.3.1 because of a compatability problem with the JSON gem ( ruby/json#229 ). To do this I just removed the old gem lock file and generated a new one.
- cf. ruby/www.ruby-lang.org#1073 (comment) - Also, need a latest json gem to fix dependencies - cf. ruby/json#229
- cf. ruby/www.ruby-lang.org#1073 (comment) - Also, need a latest json gem to fix dependencies - cf. ruby/json#229
1.8.1 is incompatible with Ruby 2.2.0. ruby/json#229
#229 (comment) seems to be back with Ruby 2.4.0 on macOS Sierra 10.12.4, Bundler 1.14.5. If I switch back to using Ruby 2.0.0p648 (which is the system default on macOS 10.12.4) have no such issue. Maybe I'm barking up the wrong tree since nobody else seems to have added a new comment here, but 🤷♂️. |
#229 issue is back with ruby 2.4. compiling generator.c An error occurred while installing json (1.7.7), and Bundler cannot continue. |
changed to branch v1.8 repo to avoid that annoying bug fbuffer.h > VALUE result = rb_str_new(FBUFFER_PTR(fb), FBUFFER_LEN(fb)); ruby/json#229 (comment)
Adds support to ruby v2.2.2 by modifying rb_str_new macro parameters. Issue: ruby#229
Have the same problem with ruby 2.3.4 on OSX Sierra. |
Seems JSON version 1.8.3 does the trick http://fuzzyblog.io/blog/ruby/2016/10/11/what-to-do-when-bundle-install-fails-with-json-1-8-1.html |
Seems I ran into ruby/json#229
I upgraded to Ruby 2.2.0, but now I get errors when I install the JSON gem:
I don't see anything about
rb_str_new
in the Ruby 2.2.0 change log, so maybe I just have something wrong with my environment? Any tips would be appreciated.The text was updated successfully, but these errors were encountered: