[Ffmpeg-devel] [patch] lib64 in libxxx.pc

sean darcy seandarcy2
Sun Dec 24 16:35:41 CET 2006


On 12/23/06, Diego Biurrun <diego at biurrun.de> wrote:
> Please keep ffmpeg-devel in the loop.
>
> On Sat, Dec 23, 2006 at 02:02:40PM -0500, sean darcy wrote:
> > On 12/22/06, Diego Biurrun <diego at biurrun.de> wrote:
> > >Oh, this patch is ancient ...
> > >
> > >On Sun, Jun 11, 2006 at 06:31:39PM -0400, sean wrote:
> > >> configure creates the libdir in the .pc files with:
> > >>
> > >> libdir=\${exec_prefix}/lib
> > >>
> > >> which causes a problem for those like me who have the ffmpeg
> > >> libs in /usr/lib64.
> > >>
> > >> configure does know the libdir - it's $libdir. So this patch
> > >>  sets the libdir using it:
> > >>
> > >> libdir=$libdir
> > >
> > >That won't work either since then you will end up with something like
> > >'libdir=${PREFIX}/lib64'.
> > >
> > >Another problem is that the libpostproc include path ends up wrong since
> > >it's not $prefix/include/ffmpeg but $prefix/include/postproc (why?).
> > >
> > >I don't see a quick and easy fix for this short of restructuring all of
> > >this path handling in configure.
> >
> > I thought you'd applied the patch, because ffmpeg svn 7328  -
> > unpatched - puts the .pc files in lib64 on my machine:
> >
> > locate libpostproc.pc libavcodec.pc libavutil.pc libavformat.pc
> > /usr/lib64/pkgconfig/libavcodec.pc
> > /usr/lib64/pkgconfig/libavformat.pc
> > /usr/lib64/pkgconfig/libavutil.pc
> > /usr/lib64/pkgconfig/libpostproc.pc
> >
> > For whatever reason, it now works :)
>
> I very much doubt it.  Have you looked at the files' contents?
>
> Diego
>

Ah yes.

You're right, of course. They point to /usr/lib/ .

I've  manually fixed them.

sean




More information about the ffmpeg-devel mailing list