From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3 v2] xorg: fix installation paths (branch yem/xorg)
Date: Sun, 24 Apr 2016 18:16:44 +0200 [thread overview]
Message-ID: <20160424161644.GB2583@free.fr> (raw)
In-Reply-To: <20160421220137.4a88ed00@free-electrons.com>
Thomas, All,
On 2016-04-21 22:01 +0200, Thomas Petazzoni spake thusly:
> 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?
(trying to reconnect the dots...)
Right. But in turns out that pkg-config has been fixed, yet there still
are errors, because the Xorg packages define an "sdk_dir" (or so)
variable, and use that to prefix a lot of directories, of which the
runtime directories.
So, it's not about a pkg-config issue, but mainly because all of the
Xorg packages are bran-damaged and try (and fail) to circumvent
pkg-config functionality by setting variables that are not common
pkg-config variables.
I did not correctly update the cover letter from the previous iteration,
sorry... I can rewrite it and respin the series, but the patches will
not change.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-04-24 16:16 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 ` [Buildroot] [PATCH 0/3 v2] xorg: fix installation paths (branch yem/xorg) Thomas Petazzoni
2016-04-24 16:16 ` Yann E. MORIN [this message]
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=20160424161644.GB2583@free.fr \
--to=yann.morin.1998@free.fr \
--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