Summary: | dev-ruby/ruby-gstreamer-0.19.4 fails, undefined references in extension | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Diego Elio Pettenò (RETIRED)
![]() Created attachment 232069 [details]
Build log
+ruby-1.8.7_p249-r2.ebuild: Also use --no-undefined as it's done for 1.9. This is the cause of this bug. My strong suggestion is to back out this change. The fact that 1.9 does this by default is nice, but let's cross that bridge when we get to it. There's plenty of stuff to do for ruby that we don't need to actively look for trouble here. I think this is much more likely an exceptional false positive than a rule; and at the same time, at least it has shown us that there _is_ a bug: ruby-gstreamer depends on presence, and load, of something (likely ruby-glib) to provide those symbols. Let's call this FIXED but it's really worked around in the ruby-ng-gnome2 eclass. |