Hi, I'd like to ask ... I am trying to compile ffmpeg plugin for qmmp, but cmake fails to recognize the needed libraries: ... snip ... -- checking for modules 'libavcodec;libavformat' -- package 'libavcodec' not found -- package 'libavformat' not found ... snip ...

The relevant CMakeLists.txt line is: pkg_check_modules(FFMPEG libavcodec libavformat)

I've also tried to run pkg-config on commandline: [root@dhcp-lab-227 rhel]# pkg-config libavcodec; echo $? 1 [root@dhcp-lab-227 rhel]# pkg-config libavformat; echo $? 1

Hi, > > I'd like to ask ... I am trying to compile ffmpeg plugin for > > qmmp, but cmake fails to recognize the needed libraries: > > > > ... snip ... > > -- checking for modules 'libavcodec;libavformat' > > -- package 'libavcodec' not found > > -- package 'libavformat' not found > > ... snip ... > > Are you sure ffmpeg-devel from the EL-5 testing repository was > actually installed on the buildroot ? yes, I am pretty sure that it is available as I am trying that live on my system (I mean manually running cmake, or make x86_64) > > I've also tried to run pkg-config on commandline: > > > > [root@dhcp-lab-227 rhel]# pkg-config libavcodec; echo $? > > 1 > > [root@dhcp-lab-227 rhel]# pkg-config libavformat; echo $? > > 1 > > you don't have requested anything at this time. So an empty > result was expected. as far as I understand the docs, the exitcode indicates whether the package can be used or not - 0 (on Fedora) is ok, 1 is bad > Try with: > [root@kwizatz firmware]# pkg-config libavcodec --libs > -lavcodecrpmfusion (yes, this is my own tweaked version, > should have been -lavcodec). well, now it gets interesting: [root@dhcp-lab-227 10]# pkg-config libavcodec --libs Package libraw1394 was not found in the pkg-config search path. Perhaps you should add the directory containing `libraw1394.pc' to the PKG_CONFIG_PATH environment variable Package 'libraw1394', required by 'libavcodec', not found and the Fedora machine: [root@F10 ~]# pkg-config libavcodec --libs -lavcodec so let's try yum install libraw1394-devel: [root@dhcp-lab-227 10]# pkg-config libavcodec --libs Package theora was not found in the pkg-config search path. Perhaps you should add the directory containing `theora.pc' to the PKG_CONFIG_PATH environment variable Package 'theora', required by 'libavcodec', not found ok, then yum install libtheora-devel: [root@dhcp-lab-227 10]# pkg-config libavcodec --libs -lavcodec [root@dhcp-lab-227 10]# pkg-config libavformat; echo $? 0 voila! - cmake can now detect ffmpeg correctly thanks for the inspiration what to try /me is going to file a bug about missing dependencies now

2009/1/20 Dominik 'Rathann' Mierzejewski <dominik(a)greysector.net&gt;: > They're not missing. Most probably the .pc file is broken or it's a bug > in pkg-config. We are talking about the EL-5 ffmpeg-devel here. Nah, this is a bug in ffmpeg-devel package (meant the pc files) Because they have something like Requires.private: libraw1394 And the ffmpeg-devel doesn't requires libraw1394-devel where the libraw1394.pc is so it doesn't have any chance to output the requested information. Actually, the current situation avoid the problem in the ffmpeg pkg-config files by using libs.private with the non-pkgconfig form for defining used libraries (instead of the pkg-config form using requires.private).

It turned out to be an old bug in ffmpeg's pkgconfig file generation. Fixed by applying an upstream patch.

> chain-build as > http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji#C >hained_builds suggests That is (as the URL indicates) koji specific. Our buildsys (just like the plague for EPEL) automatically picks up everything that finished building as BR.

IOW: Just run "make build" and it'll pick up the new ffmpeg.

> huh, never seen such error ... but Google knows, and it > suggests that macro %cmake is not defined; Do you, BuildRequires: cmake

Which pkg is this,

targetting what (EL-5)?

Odd indeed, I've been able to build several cmake-based apps in epel, taglib, for example: http://buildsys.fedoraproject.org/logs/fedora-5-epel/354-taglib-1.5-2.el5... compare/contrast: http://buildsys.rpmfusion.org/logs/el-5-rpmfusion_free/2619-qmmp-plugins-... Offhand, I'm stimied.

> Something else is strange here: > > http://buildsys.rpmfusion.org/logs/el-5-rpmfusion_free/2619-qmmp-plugins-... > > [...] > warning: Could not canonicalize hostname: fusionbuilder64 > Building target platforms: i386 > Building for target i386 > [...] > Executing /usr/sbin/mock-helper yum --installroot /var/lib/mock/el-5-i386-rpmfusion_free-cc506392f44a1c84b72c3603c074e7d97ded35d9/root resolvedep 'cmake' 'ffmpeg-devel >= 0.4.9-0.51.20080908' 'libmad-devel' 'qmmp = 0.2.3' 'taglib-devel' 'curl-devel' 'qt4-devel >= 4.2' > Excluding Packages in global exclude list > Finished > 0:cmake-2.4.8-3.el5.i386 > 0:ffmpeg-devel-0.4.9-0.51.20080908.el5.x86_64 > [...] > > x86_64 -devel for i386 build? Okay, needsign is an all-archs-in-one repo, > but why does it even consider using x86_64 pkgs? Because x86_64 wins over i386 (better arch) in the rpm mind.

Actually, in the mock config files, only the i?86 packages are excluded from the x86_64 arch. Which make sense since most of the time, only the x86_64 repository is multiarch. But as the needsign repository is also multiarch, the problem would appears on i386 too. I don't know what prevent that from the fedora's builder, but I will need to exclude the x86_64 packages from the i386 rpmfusion mock files if added to the cfg. (will be disabled by default).

On Fri, Jan 30, 2009 at 06:14:46PM +0100, Michael Schwendt wrote: >>> 0:cmake-2.4.8-3.el5.i386 >>> 0:ffmpeg-devel-0.4.9-0.51.20080908.el5.x86_64 >>> [...] >>> >>> x86_64 -devel for i386 build? Okay, needsign is an all-archs-in-one repo, >>> but why does it even consider using x86_64 pkgs? >> Because x86_64 wins over i386 (better arch) in the rpm mind. > Pardon? This is a build for target i386. It must not look at any x86_64 This also happened on my builder (lisas.de) before Thorsten deleted/renamed /etc/rpm/platform. If this contains "x86_64-..." yum/rpm will always look at x86_64 packages even it should only look at i386.