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 796447 - gstreamer mac os pkg installer have wrong library path
gstreamer mac os pkg installer have wrong library path
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: cerbero
1.14.1
Other Mac OS
: Normal blocker
: 1.14.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 796536 796750 796800 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2018-05-29 15:45 UTC by Wan Hing Wah
Modified: 2018-08-08 19:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Wan Hing Wah 2018-05-29 15:45:34 UTC
I download the pkg installer in
https://gstreamer.freedesktop.org/data/pkg/osx/1.14.1/ for runtime and devel pkg

After installation, when trying to launch gst-launch-1.0, 
it report a image not found error:

````
$ /Library/Frameworks/GStreamer.framework/Commands/gst-launch-1.0
dyld: Library not loaded: /Users/matt/Projects/cerbero-1.14/build/dist/darwin_x86_64/lib/libgstreamer-1.0.0.dylib
  Referenced from: /Library/Frameworks/GStreamer.framework/Commands/gst-launch-1.0
  Reason: image not found
Abort trap: 6

```

I have to set DYLD_FALLBACK_LIBRARY_PATH  to /Library/Frameworks/GStreamer.framework/Libraries in order to run the tool


Moreover, the *.pc files have also wrong path set:
```
 $cat /Library/Frameworks/GStreamer.framework/Versions/1.0/lib/pkgconfig/gstreamer-plugins-base-1.0.pc
prefix=/Users/matt/Projects/cerbero-1.14/build/dist/darwin_x86_64
exec_prefix=${prefix}
libdir=/Users/matt/Projects/cerbero-1.14/build/dist/darwin_x86_64/lib
includedir=${prefix}/include/gstreamer-1.0
pluginsdir=/Users/matt/Projects/cerbero-1.14/build/dist/darwin_x86_64/lib/gstreamer-1.0

Name: GStreamer Base Plugins Libraries
Description: Streaming media framework, base plugins libraries
Requires: gstreamer-1.0
Version: 1.14.1
Libs: -L${libdir}
Cflags: -I${includedir}
```
Comment 1 Tim-Philipp Müller 2018-06-08 09:30:02 UTC
*** Bug 796536 has been marked as a duplicate of this bug. ***
Comment 2 Tim-Philipp Müller 2018-06-08 09:38:01 UTC
How does this compare to 1.14.0 exactly? Could you give examples/side-by-side?

It's unclear to me right now why it would be different or what changed. (Other than Users/matt vs. Users/jan).
Comment 3 Jan Schmidt 2018-06-08 09:43:57 UTC
Might be related to commit 64a76ad (cerbero)

commit 64a76adc9aa6e12642255201cbca546015ffd7b2
Author: Sebastian Dröge <sebastian@centricular.com>
Date:   Tue Apr 24 18:04:08 2018 +0300

    Fix generation of fat shared libraries on macOS
    
    We have to properly check which of the prefixes is a parent directory of
    our file, not via string comparisions. Otherwise "/foo/x86" and
    "/foo/x86_64" or both considered parents of "/foo/x86_64/bar" and which
    one is stripped from the path depends on the order.
    
    Thanks to Mathieu Duponchelle for the non-ugly generator-based function
    for doing this check.
Comment 4 Ben Singer 2018-06-13 21:33:18 UTC
1.14.0 and earlier has /Library/Frameworks in place of /Users/matt/... in the rpath. One of our users got same error reported here, and I did as well. Reverting to 1.14.0 fixed the issue. Could fix via install_named_tool posthoc or in the link step I imagine.
Comment 5 Andy Robinson 2018-07-01 11:27:27 UTC
Is there a workaround for this? If not then I do hope it will be fixed in 1.14.2
Comment 6 Wan Hing Wah 2018-07-01 11:31:42 UTC
my workaround is to use homebrew to install gstreamer instead of pkg file from gstreamer  website
Comment 7 Jan Schmidt 2018-07-02 15:02:45 UTC
Turns out Matt used the wrong build command to roll the MacOS binaries. 1.14.2 will be fixed, and should be out this week we hope.
Comment 8 Jan Schmidt 2018-07-05 15:48:27 UTC
*** Bug 796750 has been marked as a duplicate of this bug. ***
Comment 9 Matthew Waters (ystreet00) 2018-07-12 14:45:07 UTC
*** Bug 796800 has been marked as a duplicate of this bug. ***
Comment 10 Tim-Philipp Müller 2018-08-08 11:40:29 UTC
Is this fixed with the 1.14.2 binaries now?
Comment 11 Ben Singer 2018-08-08 19:06:37 UTC
(In reply to Tim-Philipp Müller from comment #10)
> Is this fixed with the 1.14.2 binaries now?

Yes
Comment 12 Tim-Philipp Müller 2018-08-08 19:27:55 UTC
Great, thanks for confirming.