Bug #12071: Gem installation fails with 2.3.0 on Cygwin

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-cygwin]
• Backport: 2.1: DONTNEED, 2.2: REQUIRED, 2.3: DONE

[Panyamin (Benjamin Gueroult)]

Hello,

I would like report an issue when installing gem on Cygwin with ruby 2.3.0.

Backtrace is:

/home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- win32/resolv (LoadError)
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:971:in `default_config_hash'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:989:in `block in lazy_initialize'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:982:in `synchronize'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:982:in `lazy_initialize'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:360:in `block in lazy_initialize'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:358:in `synchronize'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:358:in `lazy_initialize'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:518:in `fetch_resource'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:512:in `each_resource'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/2.3.0/resolv.rb:493:in `getresource'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/remote_fetcher.rb:99:in `api_endpoint'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/source.rb:47:in `api_uri'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/source.rb:183:in `load_specs'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/spec_fetcher.rb:263:in `tuples_for'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/spec_fetcher.rb:238:in `block in available_specs'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/source_list.rb:98:in `each'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/source_list.rb:98:in `each_source'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/spec_fetcher.rb:223:in `available_specs'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/spec_fetcher.rb:103:in `search_for_dependency'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/commands/update_command.rb:118:in `fetch_remote_gems'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/commands/update_command.rb:140:in `highest_remote_version'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/commands/update_command.rb:268:in `block in which_to_update'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/commands/update_command.rb:264:in `each'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/commands/update_command.rb:264:in `which_to_update'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/commands/update_command.rb:97:in `execute'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/command.rb:308:in `invoke_with_build_args'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/command_manager.rb:169:in `process_args'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/command_manager.rb:139:in `run'
        from /home/USER/.rbenv/versions/2.3.0/lib/ruby/site_ruby/2.3.0/rubygems/gem_runner.rb:55:in `run'
        from /home/USER/.rbenv/versions/2.3.0/bin/gem:21:in `<main>'

I fixed the issue with the attached patch, but I'm not sure if this is the correct way...

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Feedback

Since Cygwin does not have its own resolv.conf file, it is not correct.
How did you install ruby, and did fiddle get installed successfully?
Please show mkmf.log files under ext/fiddle and ext/win32.

[Panyamin (Benjamin Gueroult)]

• File fiddle.mkmf.log fiddle.mkmf.log added

Nobuyoshi Nakada wrote:

How did you install ruby, and did fiddle get installed successfully?

I installed with rbenv, and I'm pretty sure that it doesn't work with the "common way". I can test if you want?

Please show mkmf.log files under ext/fiddle and ext/win32.

You'll find fiddle mkmf.log attached.
I found nothing in win32. Which meaning compilator didn't even entered in it..?

Thanks !

[nobu (Nobuyoshi Nakada)]

Does fiddle get installed and work?
win32 requires it.

[Panyamin (Benjamin Gueroult)]

Nobuyoshi Nakada wrote:

Does fiddle get installed and work?
win32 requires it.

Well, I've found some snippets on using fiddle, and it's working.

I guess during compilation ext/win32 dir isn't even entered.

[Panyamin (Benjamin Gueroult)]

Note that when compiling 2.2.4, win32 is entered because there is mkmf.log.

[Panyamin (Benjamin Gueroult)]

• File config.log config.log added
• File ruby-build.20160218233708.3584.log ruby-build.20160218233708.3584.log added

If this can help you, here is the config.log and build.log from compilation.

[nobu (Nobuyoshi Nakada)]

• Backport changed from 2.3: UNKNOWN to 2.3: REQUIRED

[nobu (Nobuyoshi Nakada)]

• Status changed from Feedback to Closed

[Panyamin (Benjamin Gueroult)]

Awesome, thank you!

[naruse (Yui NARUSE)]

• Backport changed from 2.3: REQUIRED to 2.1: DONTNEED, 2.2: DONTNEED, 2.3: REQUIRED

[naruse (Yui NARUSE)]

• Backport changed from 2.1: DONTNEED, 2.2: DONTNEED, 2.3: REQUIRED to 2.1: DONTNEED, 2.2: DONTNEED, 2.3: DONE

ruby_2_3 r54406 merged revision(s) 53868.

[hedgehog (Hedge Hog)]

This issue is also present in ruby 2.2.6. Should I open a new issue or does it suffice to note this here?

[nobu (Nobuyoshi Nakada)]

• Backport changed from 2.1: DONTNEED, 2.2: DONTNEED, 2.3: DONE to 2.1: DONTNEED, 2.2: REQUIRED, 2.3: DONE

No, you don't have to open a new issue.
Changed Backport now.

[usa (Usaku NAKAMURA)]

• Status changed from Closed to Feedback

Is this problem really present in ruby 2.2 ?
I've never backported default_exclude_exts feature.

[hedgehog (Hedge Hog)]

Yes this issue is present in 2.2.6.
When I checked the logs I saw the same symptoms reported here.
When I checked the 2.2.6 source code on my local machine it appeared that change in revision 53868 was also required there in the 2.2.6 source:

https://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/ext/extmk.rb?r1=53448&r2=53868&pathrev=53868

Unfortunately I am on leave and don't have access to my windows machine.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Feedback to Closed