weechat's Ruby bindings fail to build with ruby 1.9. Since they use the default interpreter, this can cause problems. Until upstream fixes that, it should explicitly use Ruby 1.8. Something like the attached patch should fix that.
Created attachment 181395 [details, diff] propsed patch
I can't reproduce this with weechat-0.2.6.2 and ruby-1.9.1_p243. Is this still a bug?
There is nothing in the Changelog of weechat to suggest that this got fixed on their end at least for any of the 0.2.6 versions, but maybe something changed on the ruby 1.9 end. Alex?
Ruby is silently ignored now... alex@neon weechat % USE="ruby" ebuild weechat-0.2.6.2.ebuild install ... Following components were asked but not found, they will not be built: ruby gnutls Interfaces........................ : ncurses Build with GNUtls support......... : no Build with flock support.......... : yes Build with Plugin support......... : yes Perl plugin......... : yes (5.8.8) Python plugin....... : yes (2.6) Ruby plugin......... : no Lua plugin.......... : no Aspell plugin....... : no Charset plugin...... : yes Compile with debug info........... : no Backtrace........... : yes Build doc..........................: Print debugging messages.......... : no I guess they look for a versionless libruby.so which does no longer exist.
This works fine for me with just ruby 1.8.7 installed: Build with Plugin support......... : yes Perl plugin......... : yes (5.8.8) Python plugin....... : yes (2.6) Ruby plugin......... : yes (1.8) Lua plugin.......... : no Does this mean that we can close this bug since ruby 1.9 will be ignored?
This is still not resolved. We'd like to unmask ruby:1.9 in the near future. Newer weechat packages use cmake, and my patch no longer works and I lack the cmake-fu to fix it. scarabeus, you should get the idea of the patch, can you please take care of that?
I think this issue is gone as the weechat changelog indicates Ruby >=1.9.1 support was added in 0.3.1. Seems to build fine for me with 1.9.1p243
Hopefully fixed in main tree.
