On Sun, Nov 15, 2015 at 8:03 AM, Frank Groeneveld < frank+openbsd-po...@frankgroeneveld.nl> wrote:
> On 11/12/15 07:53, Jeremy Evans wrote: > >> Attached is a port for ruby 2.3.0-preview1. This is useful if you want >> to test your ruby software to make sure it will run on ruby 2.3, but it >> won't be committed till the ruby 2.3.0 final release in late December. >> >> Release announcement is at: >> https://www.ruby-lang.org/en/news/2015/11/11/ruby-2-3-0-preview1-released/ >> > > Thanks, good work preparing for the release like this! I tested it out and > receive errors like this when installing some gems (json, sqlite3) using > bundler 1.3.5 from ports: > > Installing json (1.8.3) > Gem::Ext::BuildError: ERROR: Failed to build gem native extension. > > current directory: > /home/frank/.gem/ruby/2.3/gems/json-1.8.3/ext/json/ext/generator > /usr/local/bin/ruby23 -r ./siteconf20151115-14676-coy40a.rb extconf.rb > creating Makefile > > current directory: > /home/frank/.gem/ruby/2.3/gems/json-1.8.3/ext/json/ext/generator > make "DESTDIR=" clean > > current directory: > /home/frank/.gem/ruby/2.3/gems/json-1.8.3/ext/json/ext/generator > make "DESTDIR=" > compiling generator.c > linking shared-object json/ext/generator.so > > current directory: > /home/frank/.gem/ruby/2.3/gems/json-1.8.3/ext/json/ext/generator > make "DESTDIR=" install > /usr/ports/pobj/ruby-2.3.0-preview1/bin/install -c -m 0755 generator.so > ./.gem.20151115-14676-1oavqqb/json/ext > /usr/ports/pobj/ruby-2.3.0-preview1/bin/install: not found > *** Error 1 in > /home/frank/.gem/ruby/2.3/gems/json-1.8.3/ext/json/ext/generator > (Makefile:186 'install-so') > > make install failed, exit code 1 > > Gem files will remain installed in > /home/frank/.gem/ruby/2.3/gems/json-1.8.3 for inspection. > Results logged to > /home/frank/.gem/ruby/2.3/extensions/x86_64-openbsd/2.3/json-1.8.3/gem_make.out > > An error occurred while installing json (1.8.3), and Bundler cannot > continue. > Make sure that `gem install json -v '1.8.3'` succeeds before bundling. > > Do you think this is a bug in the port? You can reproduce this by running: > git clone https://github.com/ivaldi/brimir > bundle install --path ~/.gem > > Let me know if I can help or re-test. There's various ports that don't build without modifications (textproc/ruby-nokogiri) or that have issues at runtime with ruby 2.3.0-preview1 (www/ruby-capybara). Hopefully these issues will be fixed before the ruby 2.3.0 final release, but they aren't a bug in the port as far as I know. If you believe this is a bug in the port itself, please provide a diff or at least a reason why you think that. Note that the json gem ships with ruby since 1.9. Instead of bundle install, try: gem23 install -G ~/.gem --conservative Thanks, Jeremy
