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 796800 - gmp.h Points to Incorrect Path
gmp.h Points to Incorrect Path
Status: RESOLVED DUPLICATE of bug 796447
Product: GStreamer
Classification: Platform
Component: dont know
1.14.1
Other Mac OS
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-07-12 14:40 UTC by dan
Modified: 2018-07-12 14:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dan 2018-07-12 14:40:09 UTC
The most recent GStreamer package is installing a header file that has an incorrect hardcoded path that causes linker errors on OSX. The file is within the base-crypto package - not clear on which component that falls under. Sorry!

Inside the GStreamer 1.14.1 Devel package for OSX, 
Inside the base-crypto-devel-1.14.1-x86_64.pkg, 
Inside the Headers folder, 
Then x86_64 folder,
Is the header in question: gmp.h

Near the end of the file, __GMP_CFLAGS is defined using a hard (and incorrect) path - currently pointing to a user directory from the developer machine:
#define __GMP_CFLAGS " -Wall -g -O2 -arch x86_64 -m64 -Wno-error=format-nonliteral   -I/Users/matt/Projects/cerbero-1.14/build/dist/darwin_x86_64/include  [remainder truncated for clarity]

Previous versions (as recent as 1.14.0) pointed to the correct installed location:
#define __GMP_CFLAGS " -Wall -g -O2 -arch x86_64 -m64 -Wno-error=format-nonliteral  -I/Library/Frameworks/GStreamer.framework/Versions/1.0/include [remainder truncated for clarity]

Path should be updated from /Users/matt/Projects/cerbero-1.14/build/dist/darwin_x86_64/include back to the installed location /Library/Frameworks/GStreamer.framework/Versions/1.0/include
Comment 1 Matthew Waters (ystreet00) 2018-07-12 14:45:07 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 796447 ***