Bug 998845
Summary: | Binary extensions cannot be loaded from %gem_extdir from an scl namespace other than ruby193 | |||
---|---|---|---|---|
Product: | Red Hat Software Collections | Reporter: | Mrugesh Karnik <mkarnik> | |
Component: | ruby | Assignee: | Josef Stribny <jstribny> | |
Status: | CLOSED ERRATA | QA Contact: | Iveta Wiedermann <isenfeld> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | ruby193 | CC: | hhorak, isenfeld, jstribny, sochotni, vondruch | |
Target Milestone: | --- | |||
Target Release: | 1.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | ruby193-ruby-1.9.3.484-43.el6,ruby193-ruby-1.9.3.484-43.el7 | Doc Type: | Bug Fix | |
Doc Text: |
Cause: When binary extensions are installed under %gem_extdir/lib/ in a software collection that installs under a namespace other than ruby193, it cannot be loaded.
Consequence: Collection which depends on ruby193 would not be able to properly use rubygem- packages, which ships binary extensions.
Fix: RubyGems from ruby193 collection can now properly discover locations of binary extensions for dependent collections.
Result: rubygem- package from depending collections, which ships with binary extensions, can be properly loaded now.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1034639 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-04 07:15:50 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1034639 |
Description
Mrugesh Karnik
2013-08-20 08:08:06 UTC
Thanks for your report. The Ruby support for binary extensions was never designed in a way to support multiple roots, hence the binary extension path is derived from Ruby location. Unfortunately, since your gems are in different SCL root, Ruby has no clue about it. The possible solution might be to take GEM_PATH environment variable during evaluation of binary extension location. Moving to 1.1.0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0619.html |