On Tue, May 11, 2010 at 10:44:40AM +0200, Reinhard Tartler wrote: > The following message is a courtesy copy of an article > that has been posted to gmane.linux.debian.devel.general as well. > > On Tue, May 11, 2010 at 10:22:02 (CEST), Philipp Kern wrote: > > > On 2010-05-11, Reinhard Tartler <siret...@debian.org> wrote: > >> [1] http://experimental.ftbfs.de/chromium-browser (unavailable at time > >> of writing) > > > > experimental.ftbfs.de is down for good. I guess you meant [0] or similar. > > > > Kind regards, > > Philipp Kern > > > > [0] > > https://buildd.debian.org/status/package.php?p=chromium-browser&suite=experimental > > Indeed. Thaks for that link! > > checking [2], reveals that I'm partly wrong. There is an in-source copy > of ffmpeg, that there is an option 'use_system_ffmpeg=1' passed to the > buildscript. This indicates that I indeed missed that upstream now > considers this. Still, I also note that a library > out/Release/obj.target/third_party/ffmpeg/libffmpeg.a is being > built. also note the following changelog comment: > > * Ops, libavutil50 is not yet in Debian, removed from depends (Closes: > #580769) > - update debian/control > > > > I can only assume that the functionality to link and use the system > ffmpeg is severely broken. One more reason to have bug #580947 at > severity serious.
From my point of view, the following needs to be done:
1) Drop ffmpeg-no-pkgconfig.patch
Using the system libraries from ffmpeg together with the
headers of a patched and more up2date ffmpeg-mt will always
result in trouble.
2) Link against the ffmpeg libraries, do not dlopen() them.
This will make shlibs work against and makes it possible to
binNMU chromium-browser in case of an ABI break in ffmpeg.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
pgpOVDgkBcfDk.pgp
Description: PGP signature
