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 789481 - gst-plugins-bad fails to build against openjpeg2 2.3.0
gst-plugins-bad fails to build against openjpeg2 2.3.0
Status: RESOLVED DUPLICATE of bug 788703
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.12.3
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-25 13:20 UTC by Florent Thiéry
Modified: 2017-10-25 13:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Florent Thiéry 2017-10-25 13:20:21 UTC
Trying to rebuild gst-plugins-bad on arch using the distro package, and it doesn't build anymore due to openjpeg2 being at version 2.3.0 instead of the version gst-plugins-bad apparently expects (2.2):

In file included from gstopenjpegdec.h:29:0,
                 from gstopenjpegdec.c:27:
gstopenjpeg.h:42:12: fatal error: openjpeg-2.2/openjpeg.h: No such file or directory
 #  include <openjpeg-2.2/openjpeg.h>
            ^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

While patching /ext/openjpeg/gstopenjpeg.h from include <openjpeg-2.2/openjpeg.h> to include <openjpeg-2.3/openjpeg.h> could work, what is the proper way to fix this ?

These are all headers included in the openjpeg2 package:

openjpeg2 /usr/include/
openjpeg2 /usr/include/openjpeg-2.3/
openjpeg2 /usr/include/openjpeg-2.3/openjpeg.h
openjpeg2 /usr/include/openjpeg-2.3/opj_config.h
openjpeg2 /usr/include/openjpeg-2.3/opj_stdint.h
openjpeg2 /usr/share/doc/openjpeg2/html/opj__includes_8h.html
openjpeg2 /usr/share/doc/openjpeg2/html/opj__includes_8h_source.html
Comment 1 Sebastian Dröge (slomo) 2017-10-25 13:28:05 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

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