Emerging kde ruby bindings seems to fail due to an error obscured somewhat by gem. Though seemingly similar to http://bugs.gentoo.org/show_bug.cgi?id=349696, creating new report for the 4.6.3 version. Reproducible: Always Steps to Reproduce: - MAKEOPTS='-j1' emerge kdebindings-ruby Emerge failing with the following gem error: ... Scanning dependencies of target calendar [ 73%] Generating calendar.rb /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:779:in `report_activate_error': Could not find RubyGem qtbindings (>= 0) (Gem::LoadError) from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:214:in `activate' from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:1082:in `gem' from /usr/local/bin/rbuic4:18 make[2]: *** [ruby/korundum/modules/plasma/examples/applets/analog-clock/calendar.rb] Error 1 make[1]: *** [ruby/korundum/modules/plasma/examples/applets/analog-clock/CMakeFiles/calendar.dir/all] Error 2 make: *** [all] Error 2 * ERROR: kde-base/kdebindings-ruby-4.6.3 failed (compile phase): * emake failed ... I cannot install qtbindings using gem directly either: ... -- --------FindRuby.cmake debug------------ -- _RUBY_POSSIBLE_EXECUTABLE_NAMES: ruby;ruby1.9;ruby19;ruby1.9.1;ruby191;ruby1.9.2;ruby192;ruby1.8;ruby18 -- _RUBY_POSSIBLE_LIB_NAMES: ruby;ruby-static;ruby1.8;ruby-1.8.7 -- RUBY_ARCH_DIR: /usr/lib64/ruby/1.8/x86_64-linux -- RUBY_HDR_DIR: nil -- RUBY_POSSIBLE_LIB_DIR: /usr/lib64 -- Found RUBY_VERSION: "1.8.7" , short: "1.8", nodot: "18" -- _RUBY_REQUIRED_VARS: RUBY_EXECUTABLE;RUBY_INCLUDE_DIR;RUBY_LIBRARY -- -------------------- CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:91 (MESSAGE): Could NOT find Ruby (missing: RUBY_LIBRARY) Call Stack (most recent call first): /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:252 (_FPHSA_FAILURE_MESSAGE) cmake/modules/FindRuby.cmake:249 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) CMakeLists.txt:18 (FIND_PACKAGE) -- Configuring incomplete, errors occurred! ... Why would RUBY_LIBRARY be missing?! Also, tried rebuilding smoke with all use flags enabled and with the "keeptemp" feature. Attached: -emerge --info -build.log -use flags -environment
Created attachment 276417 [details] emerge --info
Created attachment 276419 [details] Build log
Created attachment 276423 [details] USE flags for the merge
Created attachment 276425 [details] Ebuild environment
Hacked way to get install to work: 1) created symlink /usr/lib/libruby.so (pointing to /usr/lib64/libruby18.so) 2) gem installed qtbindings 3) emerged kdebindings-ruby 4) removed symlink This is not really a solution as it needs to be hacked on each successive update now. The two problems: - The kdebindings-ruby ebuild depends on the qtbindings gem (qt4-qtruby ebuild no longer exists?) - The /usr/lib/libruby.so symlink required by qtbindings is not created by eselect anymore The following provided some insight: http://forums.gentoo.org/viewtopic-t-813870.html https://forums.gentoo.org/viewtopic-t-733340-start-0.html http://bugs.gentoo.org/show_bug.cgi?id=265370#c5 http://bugs.gentoo.org/show_bug.cgi?id=256703
Could you please try kde-4.7.0? The bindings have been completely restructured there, and before we spend a lot of time fixing the old version... kdebindings-ruby has been replaced by korundum and krossruby.
There's one much simpler thing that we could check... what's your output of eselect ruby list ? After you re-set one ruby version, does it still fail?
(In reply to comment #7) > There's one much simpler thing that we could check... what's your output of > > eselect ruby list > > ? After you re-set one ruby version, does it still fail? Unfortunately I'm under a completely new environment now and so this report is no longer applicable. Marking as obsolete for now.