[Buildroot] [PATCH 1/1] ccid: fix build with pkgconf 1.5.3

Arnout Vandecappelle arnout at mind.be
Wed Dec 12 08:58:16 UTC 2018



On 12/12/2018 09:50, Arnout Vandecappelle wrote:
> 
> 
> On 11/12/2018 23:45, Fabrice Fontaine wrote:
>> Hello,
>> Le mar. 11 déc. 2018 à 22:57, Arnout Vandecappelle <arnout at mind.be> a écrit :
> [snip]
>>>  I can't say I really like any of these solutions though...
>> An other option would be to ignore the value provided by pkgconfig.
>> For example, we can pass
>> --enable-usbdropdir=$(TARGET_DIR)/usr/lib/pcsc/drivers to ccid's
>> configure.
>> Would it be acceptable?
> 
>  Since a good fundamental solution will take some time to flesh out, and since
> the autobuilders are exploding because of this, it's a great proposal.
> 
>  However, shouldn't it be --enable-usbdropdir=/usr/lib/pcsc/drivers? DESTDIR is
> still prepended to it, no?

 BTW, asccid [1] seems to have a similar issue.

 Thanks!

 Regards,
 Arnout

[1]
http://autobuild.buildroot.net/results/d7f1f368f11da302d8fa2b9268d5ea7bd737b5f2/build-end.log


> 
>  Put something like this in the commit message:
> 
> Since the bump to 1.5.3, pkgconf prepends the sysroot to all absolute paths
> found in the .pc file. This is correct when the paths refer to something in
> STAGING_DIR (e.g. libdir, includedir), but not when it refers to something used
> for the target.
> 
> ccid uses the usbdropdir variable from libpcsclite.pc to decide where to install
> things. Since DESTDIR is prepended to the install destination, this will end up
> in the wrong location.
> 
> Until a better solution is found in pkgconf, pass the usbdropdir to use
> explicitly instead of relying on libpcsclite.pc.
> 
> 
>  BTW, is the libva issue similar?
> 
>  Regards,
>  Arnout
> 


More information about the buildroot mailing list