From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Fix pkg-kconfig packages with ccache enabled
Date: Thu, 10 Jan 2019 22:14:57 +0100 [thread overview]
Message-ID: <20190110211500.14368-1-thomas.petazzoni@bootlin.com> (raw)
Hello,
This series addresses a problem that has been reported several times:
if you have BR2_CCACHE=y and run "make uboot-menuconfig" from a clean
tree, it fails because U-Boot tries to build the kconfig code with
ccache, but ccache has not been built yet.
To address this, we:
- Make sure to pass HOSTCC=$(HOSTCC_NOCCACHE) in the kconfig steps of
kconfig packages. This has in fact no real effect, because linux
and u-boot were overriding HOSTCC, and other packages were not
passing HOSTCC, so plain "gcc" was used.
- Fix the U-Boot case by passing HOSTCC=$(HOSTCC_NOCCACHE)
- Make the Linux case consistent with other kconfig packages by also
passing HOSTCC=$(HOSTCC_NOCCACHE)
Thanks,
Thomas
Thomas Petazzoni (3):
package/pkg-kconfig: pass HOSTCC during kconfig steps
boot/uboot: use HOSTCC_NOCCACHE as kconfig HOSTCC
linux: use HOSTCC_NOCCACHE as kconfig HOSTCC
boot/uboot/uboot.mk | 5 +++--
linux/linux.mk | 17 ++++++++++-------
package/pkg-kconfig.mk | 10 +++++++---
3 files changed, 20 insertions(+), 12 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-10 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 21:14 Thomas Petazzoni [this message]
2019-01-10 21:14 ` [Buildroot] [PATCH 1/3] package/pkg-kconfig: pass HOSTCC during kconfig steps Thomas Petazzoni
2019-01-13 21:43 ` Yann E. MORIN
2019-01-16 22:39 ` Peter Korsgaard
2019-01-28 17:01 ` Peter Korsgaard
2019-01-10 21:14 ` [Buildroot] [PATCH 2/3] boot/uboot: use HOSTCC_NOCCACHE as kconfig HOSTCC Thomas Petazzoni
2019-01-13 21:47 ` Yann E. MORIN
2019-01-13 21:51 ` Yann E. MORIN
2019-01-24 16:12 ` Arnout Vandecappelle
2019-01-16 22:39 ` Peter Korsgaard
2019-01-28 17:01 ` Peter Korsgaard
2019-01-10 21:15 ` [Buildroot] [PATCH 3/3] linux: " Thomas Petazzoni
2019-01-13 21:50 ` Yann E. MORIN
2019-01-16 22:40 ` Peter Korsgaard
2019-01-28 17:01 ` Peter Korsgaard
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=20190110211500.14368-1-thomas.petazzoni@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.