Hi all,

Reinhard Tartler schrieb:
It looks like the dependencies of libavdevice-dev are a bit messed up
as follows:
 - libavdevice-dev Depends on libavdevice52
 - libavdevice52 Depends on libdc1394-13 (*Note*: not libdc1394-22)

WTF? Why does libavdevice52 depend on the old libdc1394 library although the new one is listed first in the Build-Depends?!

 - the file /usr/lib/pkgconfig/libavdevice.pc that ships with
   libavdevice-dev should not explicitly add -llibdc1394_control
   to the build flags.

Right. This should happen automatically in ffmpeg's configure script in lines 1656ff. However, the Debian package seems to have built against the old lib - which is highly unexpected - and pulls in the new lib as a dependency for the libavformat-dev package.

Since you have changed the dependencies for libdc1394-13-dev to
libdc1394-22-dev, could you please investigate this issue? I don't know
much about firefire libs, but it seems to me that the version of ffmpeg
we ship is not prepared use the newer version. I'd therefore suggest to
revert the switch to libdc1394-22-dev, but I wanted to give you the
oppurtunity to comment on the issue.

Sure, we can switch it back. But to be honest, I cannot explain why this issue arose at all. As far as I cann tell all Build-Depends and Depends are set correctly.

We have both the new and the old lib in the Build-Depends as alternatives. Since we list the new one first, we expect ffmpeg to build against it. Thus we set the new lib as a dependency for the resulting libavformat-dev package. The package at hand has however been built against the old lib. The pkg-config file has been set correctly to link against the old lib, but we pull in the new one via the libavformat-dev dependencies.

That's strange...




--
Dipl.-Phys. Fabian Greffrath

Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum

Telefon: +49 (0)234 / 32-26334
Fax:     +49 (0)234 / 32-14227
E-Mail:  [EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to