GNOME Bugzilla – Bug 598824
gst-plugins-ugly refuse compilation if in system present installed x264
Last modified: 2009-10-23 08:42:49 UTC
As far as I understand x264 require undefined macro GST_DISABLE_GST_DEBUG but by default GST_DISABLE_GST_DEBUG is defined. It is safe undef GST_DISABLE_GST_DEBUG for normal use (non-dev)? if save how it can be done? gstx264enc.c:394:3: error: attempt to use poisoned "gst_debug_log_valist" gstx264enc.c: In function 'gst_x264_enc_log_callback': gstx264enc.c:394: warning: implicit declaration of function 'gst_debug_log_valist' gstx264enc.c:394: error: 'x264_enc_debug' undeclared (first use in this function) gstx264enc.c:394: error: (Each undeclared identifier is reported only once gstx264enc.c:394: error: for each function it appears in.)
I don't understand your description of the problem. I think you are saying that if you build GStreamer core --disable-gst-debug, then you run into trouble building gstx264enc.c. If so, then this commit should have fixed it in June: commit 0e285b3d299cebc2deaae4f3ab9fee7907d96a95 Author: Tim-Philipp Müller <tim.muller@collabora.co.uk> Date: Fri Jun 19 15:01:46 2009 +0100 x264enc, rdtmanager: fix compilation with debugging disabled
> I think you are saying that if you build GStreamer core --disable-gst-debug, then you run into trouble building gstx264enc.c GStreamer core was built with default configure options.
(In reply to comment #2) > > I think you are saying that if you build GStreamer core --disable-gst-debug, then you run into trouble building gstx264enc.c > > GStreamer core was built with default configure options. Pardon me, GStreamer core really was built with --disable-gst-debug.
Ok, I guess we can close this then. Thanks for confirming.
This bug is fixed in 0.10.13. *THANKS*