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 654817 - [bayer] compiler error/warnings when build with liborc
[bayer] compiler error/warnings when build with liborc
Status: RESOLVED DUPLICATE of bug 652677
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-18 08:29 UTC by Thijs Vermeir
Modified: 2011-07-18 08:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thijs Vermeir 2011-07-18 08:29:19 UTC 
I get this build error when building gst-plugins-bad (git) with liborc 0.4.14:

make[4]: Entering directory `/home/tvermeir/devel/jhbuild_root/gst-plugins-bad/gst/bayer'
  CC     libgstbayer_la-gstbayer.lo
  CC     libgstbayer_la-gstbayer2rgb.lo
  CC     libgstbayer_la-gstrgb2bayer.lo
  CC     libgstbayer_la-tmp-orc.lo
tmp-orc.c: In function '_backup_gst_bayer_horiz_upsample':
tmp-orc.c:413:12: error: variable 'var48' set but not used [-Werror=unused-but-set-variable]
tmp-orc.c:409:12: error: variable 'var44' set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors

make[4]: *** [libgstbayer_la-tmp-orc.lo] Error 1
make[4]: Leaving directory `/home/tvermeir/devel/jhbuild_root/gst-plugins-bad/gst/bayer'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/tvermeir/devel/jhbuild_root/gst-plugins-bad/gst/bayer'
make[2]: *** [bayer] Error 2
make[2]: Leaving directory `/home/tvermeir/devel/jhbuild_root/gst-plugins-bad/gst'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tvermeir/devel/jhbuild_root/gst-plugins-bad'
make: *** [all] Error 2
Comment 1 Thijs Vermeir 2011-07-18 08:30:36 UTC 

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