Paul van der Walt <[email protected]> writes:
> On 2015-10-21 at 21:23, quoth Ludovic Courtès:
>>> + (inputs
>>> + `(("pkg-config" ,pkg-config)
>>
>> This one should be in ‘native-inputs’ (normally ‘guix lint’ warns about
>> it.)
>>
>> OK to push with this change.
>
> Right, fixed and pushed. Is it surprising that it worked as i had it,
> though?
No. The difference between 'inputs' and 'native-inputs' is noticeable
when cross-compiling. 'inputs' are built to run on the target machine,
and 'native-inputs' are built to run on the build machine.
For example, suppose you use an x86_64 machine to cross-compile this
package to run on armhf. If you put 'pkg-config' in 'inputs', then it
would have been built to run on 'armhf', so when 'configure' tries to
run 'pkg-config' on the x86_64 build machine, it won't work.
Mark
