After building media-plugins/gst-plugins-webrtc-1.22.3 A notice appears: * QA Notice: Unresolved soname dependencies: * * /usr/lib64/gstreamer-1.0/libgstwebrtc.so: libgstwebrtcnice-1.0.so.0 * The package media-libs/gst-plugins-bad-1.22.3-r3 is installed on my system I don't know which package should supply this library. I am also unable to now the the 'webrtcbin' GST-element, most likely because of this missing library Reproducible: Always Steps to Reproduce: 1. Build media-plugins/gst-plugins-webrtc-1.22.3 2. Execute 'gst-inspect-1.0 | grep webrtcbin' Actual Results: # gst-inspect-1.0 | grep webrtcbin (gst-plugin-scanner:21792): GStreamer-WARNING **: 14:50:08.906: Failed to load plugin '/usr/lib64/gstreamer-1.0/libgstwebrtc.so': libgstwebrtcnice-1.0.so.0: cannot open shared object file: No such file or directory Expected Results: webrtcbin element is found
I can confirm that this also affects the operation of the pulseeffects app if built with webrtc support. Application builds and runs but warns on startup with the following message: (gst-plugin-scanner:3767): GStreamer-WARNING **: 10:55:16.670: Failed to load plugin '/usr/lib64/gstreamer-1.0/libgstwebrtc.so': libgstwebrtcnice-1.0.so.0: cannot open shared object file: No such file or directory
So I created a local ebuild of gst-plugins-bad and was able to get it to successfully build libgstwebrtcnice-1.0.so.0, albeit in a bit of a hackish way. What I did was add the following define: MYMESONARGS="-Dwebrtc=enabled" Now granted I did first try using a webrtc flag with the following in the multilib_src_configure ebuild function: if use webrtc; then emesonargs+=( -Dwebrtc=enabled ) fi However something in meson.eclass or in between in the inheritance tree caused that to be ignored (even though I did see that portage did briefly try to use the define early on in the configuration process). Something to note is that if you build it this way you will have to have libnice installed on your system and its ABI setting will have to match what you are using to build this gst-plugins-bad package. Hope this helps resolve the issue.
Thanks. This one is a dupe of bug 907470 where I've got some commentary already. I'll link to your comment. *** This bug has been marked as a duplicate of bug 907470 ***
