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 777167 - error: conflicting types for ‘GLsync’
error: conflicting types for ‘GLsync’
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal blocker
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-01-12 11:22 UTC by Russel Winder
Modified: 2017-01-26 11:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
output from ninja (627.81 KB, text/plain)
2017-01-12 11:22 UTC, Russel Winder 		  Details
Ninja log (476.76 KB, text/plain)
2017-01-12 11:23 UTC, Russel Winder 		  Details
Meson log (1.50 MB, text/plain)
2017-01-12 11:23 UTC, Russel Winder 		  Details
gl/meson: also check for the required headers on library check (1.76 KB, patch)
2017-01-13 00:15 UTC, Matthew Waters (ystreet00) 		none Details | Review

Description Russel Winder 2017-01-12 11:22:21 UTC 
Created attachment 343352 [details]
output from ninja

The GStreamer build using the Meson build system fails for me on Debian Sid. As requested on the email list I am starting this bug report. I am adding what I believe to be all the output from ninja -v, and also the ninja and meson log files.
Comment 1 Russel Winder 2017-01-12 11:23:05 UTC 
Created attachment 343353 [details]
Ninja log
Comment 2 Russel Winder 2017-01-12 11:23:45 UTC 
Created attachment 343354 [details]
Meson log
Comment 3 Matthew Waters (ystreet00) 2017-01-13 00:15:11 UTC 
Created attachment 343396 [details] [review]
gl/meson: also check for the required headers on library check

Could you test if this patch fixes the issue for you?
Comment 4 Russel Winder 2017-01-13 11:27:12 UTC 
What is the best workflow for trying this patch, so that I can try it and report back?
Comment 5 Matthew Waters (ystreet00) 2017-01-13 11:51:39 UTC 
1. download patch
2. cd /path/to/gst-build/subprojects/gst-plugins-bad
3. git am patch
4. ninja -C /path/to/gst-build/build
Comment 6 Russel Winder 2017-01-13 11:59:13 UTC 
And do this in a Git branch I assume so as to not disturb the master branch.

Will do this momentarily.
Comment 7 Russel Winder 2017-01-13 12:11:59 UTC 
I did a:

cd /location/of/gst-build
./git-update

and then thought:

cd /location/of/build-area
ninja git-update

and it seemed to rewrite all the ninja files before redoing the git-update.

ninja

and everything built. So I cannot now replicate the problem, so I guess it no longer exists. This was before trying the patch to the build system.

I haven't a clue why it worked now but not before – when it was reproducible.
Comment 8 Sebastian Dröge (slomo) 2017-01-26 11:53:00 UTC 
So let's close this for now