From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2,1/1] ccid: fix build with pkgconf 1.5.3
Date: Thu, 13 Dec 2018 21:20:41 +0100 [thread overview]
Message-ID: <20181213212041.21000c96@windsurf> (raw)
In-Reply-To: <20181212091517.23861-1-fontaine.fabrice@gmail.com>
Hello Fabrice,
On Wed, 12 Dec 2018 10:15:17 +0100, Fabrice Fontaine wrote:
> 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.
>
> Fixes:
> - http://autobuild.buildroot.org/results/4d4c1ba7f5d00d1b927ac01ef9851468abfbdff2
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2 (after review of Arnout Vandecappelle):
> - Drop patch to remove DESTDIR and use --enable-usbdropdir
Applied to master, thanks. I'd like to take this opportunity to thank a
lot for the work you've done on fixing the fallouts/consequences of the
pkg-config 1.5.3, which I authored and committed. I have been busy the
last few evenings, and couldn't help much with that, so I'm glad you've
been here to help with this. Many thanks for that.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-13 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 9:15 [Buildroot] [PATCH v2,1/1] ccid: fix build with pkgconf 1.5.3 Fabrice Fontaine
2018-12-13 20:20 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181213212041.21000c96@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox