From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3 v2] xorg: fix installation paths (branch yem/xorg)
Date: Thu, 21 Apr 2016 22:01:37 +0200 [thread overview]
Message-ID: <20160421220137.4a88ed00@free-electrons.com> (raw)
In-Reply-To: <cover.1457719643.git.yann.morin.1998@free.fr>
Hello,
On Fri, 11 Mar 2016 19:10:58 +0100, Yann E. MORIN wrote:
> This series is an attempt to fix the installation paths of many
> Xorg-related packages.
>
> The new pkconf bumped in d7f6d320 introduced a change in behaviour: all
> path variables returned by pkgconf are now prefixed with the sysroot
> directory.
>
> This has an impact on a lot of Xorg packages (and maybe others as well),
> since they use such paths verbatim to install files in either of:
> $(STAGING_DIR)/$(SYSROOT_DIR)/some/path
> $(TARGET_DIR)/$(SYSROOT_DIR)/some/path
One important thing that this cover letter doesn't explain is why we
don't fix pkg-config instead?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-21 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 18:10 [Buildroot] [PATCH 0/3 v2] xorg: fix installation paths (branch yem/xorg) Yann E. MORIN
2016-03-11 18:11 ` [Buildroot] [PATCH 1/3 v2] package/x11r7: introduce X11-global configure options Yann E. MORIN
2016-03-11 18:11 ` [Buildroot] [PATCH 2/3 v2] package/x11r7/*: fixup all install paths Yann E. MORIN
2016-03-11 18:11 ` [Buildroot] [PATCH 3/3 v2] core/pkg-generic: check proper package installation Yann E. MORIN
2016-04-21 20:01 ` Thomas Petazzoni [this message]
2016-04-24 16:16 ` [Buildroot] [PATCH 0/3 v2] xorg: fix installation paths (branch yem/xorg) Yann E. MORIN
2016-04-24 21:06 ` Thomas Petazzoni
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=20160421220137.4a88ed00@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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