https://bugzilla.gnome.org/show_bug.cgi?id=648589

Fixes #606662.

Now that we depend on (what will be) -base-0.10.33.

Temporary workaround until we fix this properly and check for
the ObjC warning/error flags instead of just passing CFLAGS to the
ObjC compiler.

https://bugzilla.gnome.org/show_bug.cgi?id=643939

https://bugzilla.gnome.org/show_bug.cgi?id=648004

From c3cafe1 to 46dfcea

Remove bits that were meant to suppport RTCP FIR

https://bugzilla.gnome.org/show_bug.cgi?id=648160

https://bugzilla.gnome.org/show_bug.cgi?id=646811

Refuse h264 caps without stream-format and codec_data fields for
now, to avoid creating broken files. This might cause some pipelines
that worked previously to fail. However, the move from -bad to -good
is our only chance to fix this up, so make it strict for now. We can
always change it back to be less strict in future.

https://bugzilla.gnome.org/show_bug.cgi?id=647919

Don't use g_assert() for error handling, even if they're highly unlikely.
Either we *know* that something can't happen, in which case we
should just not handle it, or we think something can happen, but it is
very very unlikely that it will ever happen, in which case we should
handle it like any other error instead of asserting.

g_assert() is best left for conditions we have control of, like checking
internal consistency of our code, not checking return values of external
code.

Fixes a bunch of warnings when compiling with -DG_DISABLE_ASSERT:
gstrtpgsmpay.c: In function 'gst_rtp_gsm_pay_handle_buffer':
gstrtpgsmpay.c:130:17: warning: variable 'rtpgsmpay' set but not used
gstspeexenc.c: In function 'gst_speex_enc_encode':
gstspeexenc.c:904:19: warning: variable 'written' set but not used
pulsesink.c: In function 'gst_pulsesink_change_state':
pulsesink.c:2725:9: warning: variable 'res' set but not used
pulsesrc.c: In function 'gst_pulsesrc_change_state':
pulsesrc.c:1253:7: warning: variable 'e' set but not used

Caused by -DG_DISABLE_ASSERT

Otherwise things won't work too well when compiling with
-DG_DISABLE_ASSERT (as we do for pre-releases and releases).

We use -DG_DISABLE_ASSERT for the pre-releases, which makes these
warnings pop up in cases that were previously covered by g_assert_not_reached()
and the like:
tvtime/greedyh.c:801:14: warning: 'scanline' may be used uninitialized in this function
matroska-mux.c:501:19: warning: 'context' may be used uninitialized in this function

The v4l2object formats list was being obtained into a local variable and
then still used from the context. Make use of the local variable.

GCC 4.6.x complains about such variable usage. Unused but set variables
were removed except that gst_oss4_mixer_slider_set_mute () now returns
the value from the call to gst_oss4_mixer_set_control_val ().

GCC 4.6.x spits warnings about such usage of variables. The variables in
raw1394 were marked with G_GNUC_UNUSED as this seemed omre appropriate.
The others were removed.

GCC 4.6.x complains about such usage.

GCC 4.6.x spits warnings about such usage of variables.

Remove some redundant operations (convubw) and use the correct variable,
t2, in the orc_overlay_bgra function.

GCC 4.6.x spits warnings about variables that are set but unused. Such
variables have been removed in blend, collectpads2 and videomixer2.

GCC 4.6.x spits warnings about variables that are unused but set. Such
variables have been removed where trivial but with comments left behind
for informational purposes in some cases.

gst_rtp_session_chain_recv_rtcp () was changed in commit 490113d4
to always return GST_FLOW_OK instead of the return value of
rtp_session_process_rtcp (), so we'll keep it that way.

GCC 4.6.x spits warnings about such variable usage. Note that some
calculations are left as comments for informative purposes.

GCC 4.6.x spits warnings about such variable usage.