[FFmpeg-devel] [PATCH] Use pkgconfig for dirac libs

[Måns Rullgård]

Diego 'Flameeyes' Petten? wrote:
> M?ns Rullg?rd <mans at mansr.com> writes:
>
>>> Are you using the command as "pkg-config" ? pkg-config is a tool that,
>>> akin to gcc, ld and others, have a CTARGET as well as a CHOST; this
>>> means that you should have an arm-unknown-linux-gnueabi-pkg-config
>>> command that looks in /usr/arm-unknown-linux-gnueabi/usr/lib/pkgconfig
>>> rather than in /usr/lib/pkgconfig .
>>
>> It *does* look there; that's not the problem.  The problem is that the
>> pkgconfig files installed there point to /usr.  Go figure.
>
> Uh? May I ask what tool is building /usr/arm-unknown-linux-gnueabi tree
> then? I'm sure enough that the (scarse) Gentoo crosscompiling supports
> generate proper .pc files that _don't_ point to /usr/lib so I'd be ready
> to expect a bug in some build tool that prepares that root...

I use Gentoo, following the instructions to the letter.  No problems at
all with non-pkgconfig packages...

>>> I just checked the configure and it uses pkg-config directly; instead it
>>> should use "${cross_prefix}pkg-config", and then it wouldn't "lie" to you
>>> anymore. Yes I know it's no the most intuitive of things, but if you
>>> think a bit about how crosscompiling is done it does fit in.
>>
>> The more I think, the more useless pkgconfig seems.  The compiler is
>> already configured to look in the cross-root.  It's pkgconfig that
>> sends it elsewhere.
>
> A properly-configured pkg-config executable shouldn't send it anywhere;
> standard non-crosscompiling pkg-config never returns -I/usr/include or
> -L/usr/lib (or -L/usr/lib64 on amd64 multilib systems); a
> properly-configured crosscompiling pkg-config will do the same...

Does such a thing exist?  The link Reinhard posted suggests that it does
not.

>> I'm not talking about the ffmpeg configure script.  I'm talking about
>> supposedly kosher autohell-generated scripts in various packages,
>> including gnu coreutils.
>>
>> If I don't use pkgconfig, everything works as expected; if I do use it,
>> all hell breaks loose.  Hence, I won't use it unless forced to.
>
> May I ask to see a config.log to make sure the right pkg-config is
> picked up? Since I do work in the field of cross-compiling I'm quite
> interested to see if there are such problems and resolve them.

I don't keep the log files around.  I'll try to remember next time I build
one of those packages, although I try to avoid the pain.

Now I'm off to stab myself repeatedly with a kitchen knife...

-- 
M?ns Rullg?rd
mans at mansr.com