From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2 v2] core: check for improper install paths (branch yem/pkg-no-double-build-dir)
Date: Tue, 3 Nov 2015 20:05:59 +0100 [thread overview]
Message-ID: <cover.1446577223.git.yann.morin.1998@free.fr> (raw)
Hello All!
URGENT! Please review...
This series adds a new post-step hook, that applies to both
install-target and install-staging, and checks that packages do not
install files in paths like:
$(TARGET_DIR)/$(O)
$(STAGING_DIR)/$(O)
Having one (or both) of those directories means that a package is
confusing DESTDIR, PREFIX and SYSROOT_DIR.
Such a confusion is currently caused by our host-pkgconf, that happilly
(but wrongly) prepends the sysroot directory to all paths it may return,
whether they be queried via one of --cflags, --cflags-only-I, --libs or
--libs-only-L, or whether they be directly queried via --variable=XXX.
Another source of confusion may come from generic-packages, wihch badly
coded custom Makefiles (even though I haven't noticed any so far, it is
bound to happen sooner or later...).
We want to detect such broken packages *ASAP* so we can fix them before
the release (or at best come up with a fallback plan).
Kown to break are quite a few packages from the Xorg stack, with more
than 15 detected so far, but maybe more since I had a contingency plan
to fix them in bulk, see previous RFC:
http://lists.busybox.net/pipermail/buildroot/2015-November/143562.html
Also, some packages that want to call moc (from Qt4 for sure, possibly
from Qt5 too) also have a similar issue, see:
http://lists.busybox.net/pipermail/buildroot/2015-October/141429.html
Although the second case is already causing build failures (and will
require a fix of its own), the first case has so far gone unnoticed (I
just stumbled on it by chance while reviewing the EFL bump series, which
is now kind of blocked by this issue).
Changes RFC -> v2:
- only keep those two patches, drop the Xorg fixups.
Regards,
Yann E. MORIN.
The following changes since commit b8527eb3c017c74c861db8b21f8a0def55988382:
poco: add patches to fix pcre link issue and library installation (2015-11-03 17:18:33 +0100)
are available in the git repository at:
git://git.busybox.net/~ymorin/git/buildroot yem/pkg-no-double-build-dir
for you to fetch changes up to fe19a41362f17e9435b0da14097ce9fecda38780:
core/pkg-generic: check proper package installation (2015-11-03 19:59:31 +0100)
----------------------------------------------------------------
Yann E. MORIN (2):
core/pkg-generic: allow step hooks to fail a step
core/pkg-generic: check proper package installation
package/pkg-generic.mk | 31 +++++++++++++++++++++++--------
1 file changed, 23 insertions(+), 8 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| 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 reply other threads:[~2015-11-03 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 19:05 Yann E. MORIN [this message]
2015-11-03 19:06 ` [Buildroot] [PATCH 1/2 v2] core/pkg-generic: allow step hooks to fail a step Yann E. MORIN
2015-11-03 22:07 ` Arnout Vandecappelle
2015-11-04 13:20 ` Thomas Petazzoni
2015-11-03 19:06 ` [Buildroot] [PATCH 2/2 v2] core/pkg-generic: check proper package installation Yann E. MORIN
2015-11-03 22:31 ` Arnout Vandecappelle
2015-11-04 17:19 ` Yann E. MORIN
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=cover.1446577223.git.yann.morin.1998@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