Fix pkg-kconfig packages with ccache enabled
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | package/pkg-kconfig: pass HOSTCC during kconfig stepspackage/ | +7 | 3 replies | |
| 2/3 | boot/uboot: use HOSTCC_NOCCACHE as kconfig HOSTCCboot/ | +3 | 5 replies | |
| 3/3 | linux: use HOSTCC_NOCCACHE as kconfig HOSTCClinux/ | +10 | 3 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Yann E. MORIN |
|---|---|
| 1/3 | A-b |
| 2/3 | A-b |
| 3/3 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [Buildroot] [PATCH 0/3] Fix pkg-kconfig packages with ccache enabled
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(-)
Signature · 1 line
2.20.1