[gstreamer-bugs] [Bug 340762] faad2 RPM packages incompatible

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=340762
 GStreamer | gst-plugins-bad | Ver: 0.10.3


Michael Smith changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msmith at fluendo.com




------- Comment #4 from Michael Smith  2006-05-09 09:10 UTC -------
I haven't looked into any details of this bug, but the FAAD situation in
general is extremely broken:

  1) Upstream hasn't done any releases in years.
  2) Upstream CVS is ABI incompatible with the most recent release
     (I think at least some distributions use CVS snapshots, rather than the
release?)
  3) Upstream CVS is API incompatible with the most recent release. It has a
layer of macro-compatibility shims, but...
  4) Upstream CVS AND the latest release both have broken public headers, that
declare two functions incorrectly (in a way that only breaks on 64 bit
systems). We have a Truly Evil Hack that redefines these things locally
correctly, but this breaks the API-compatibility hacks.

The end result is: we only compile against the latest release, NOT against
upstream CVS. Might be possible to work around given sufficient energy. Due to
ABI incompatibilities, we also don't link against CVS. Nothing we can do about
that part.

At a guess, this bug involves this problem in some way.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.