After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 755273 - Incorrect shared object name on OSX
Incorrect shared object name on OSX
Status: RESOLVED DUPLICATE of bug 751204
Product: GStreamer
Classification: Platform
Component: cerbero
1.5.90
Other Mac OS
: Normal critical
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-09-19 20:38 UTC by mspiegelmock
Modified: 2018-05-04 13:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description mspiegelmock 2015-09-19 20:38:48 UTC 
Trying to run a gstreamer app using http://gstreamer.freedesktop.org/data/pkg/osx/1.5.90.1/

PKG_CONFIG_PATH=/Library/Frameworks/GStreamer.framework/Versions/1.0/lib/pkgconfig go run -v client/camrelay.go 
github.com/ziutek/glib
github.com/revmischa/gst
github.com/revmischa/panoptic
command-line-arguments
dyld: Library not loaded: /Library/Frameworks/GStreamer.framework/Versions/1.0/lib/libgstreamer-1.0.0.dylib
  Referenced from: /var/folders/ln/vzj6j1h50yv98gx59cwbrfbc0000gn/T/go-build543199643/command-line-arguments/_obj/exe/camrelay
  Reason: image not found
signal: trace/BPT trap


Also sucks that I have to set PKG_CONFIG_PATH manually but my main issue is that the dylib reference is wrong. It should be -1.0.dylib
Comment 1 Jan Schmidt 2015-09-20 15:22:29 UTC 
I think this is the same as bug 735963, and related to bug 751204
Comment 2 Sebastian Dröge (slomo) 2016-02-17 14:37:08 UTC 
Not really a blocker as it's no regression and things seem to be generally working for people
Comment 3 Sebastian Dröge (slomo) 2018-05-04 13:29:01 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 751204 ***