buildroot/package/ccache, branch 2017.02

ccache: Patch to fix toolchain-wrapper's --sysroot

2017-01-27T08:57:23+00:00

ccache doesn't rewrite the --sysroot base_dir from toolchain-wrapper correctly. Resulting in a large number of cache misses when building from different base directories. A fix has already been accepted to the ccache upstream[1], but won't be released until ccache 3.4. (Was noted as an improvement, so unsure of the 3.4 release timing) [1] https://github.com/ccache/ccache/pull/132 Signed-off-by: Brandon Maier Signed-off-by: Matt Weber Signed-off-by: Thomas Petazzoni

package/ccache: bump to version 3.3.3

2016-11-08T08:37:16+00:00

Note, that version 3.3.3 of ccache fixes a bug [1] where the Linux kernel image is the same even after changing the source code and rebuilding it. [1] https://github.com/ccache/ccache/issues/136 Signed-off-by: Jörg Krause Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

ccache: bump to version 3.3.2

2016-10-05T07:53:01+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

ccache: bump to version 3.3.1

2016-09-15T09:55:54+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

ccache: bump to version 3.3

2016-08-29T21:21:22+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

ccache: bump to version 3.2.5

2016-04-19T19:16:58+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

ccache: bump to version 3.2.4

2015-10-31T08:47:14+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

ccache: bump to version 3.2.3

2015-10-07T10:31:36+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

ccache: use mtime for external toolchain, CONF_OPTS for internal toolchain

2015-10-04T16:22:21+00:00

Our current ccache disables hashing of the compiler executable itself, because using the default 'mtime' doesn't work in buildroot: we always rebuild the compiler, so the mtime is always different, so the cache always misses. However, in the current situation, if a user changes the compiler configuration (which would result in the compiler generating different object files than before) and does 'make clean all', ccache may in fact reuse object files from the previous run. This rarely gives problems, because (1) the cache expires quite quickly (it's only 1GB by default), (2) radically changing compiler options will cause cache misses because different header files are used, (3) many compiler changes (e.g. changing -mtune) have little practical effect because the resulting code is usually still compatible, (4) we currently don't use CCACHE_BASEDIR, and almost all object files will contain an absolute path (e.g. in debug info), so when building in a different directory, most of it will miss, (5) we do mostly build test, and many of the potential problems only appear at runtime. Still, when ccache _does_ use the wrong cached object files, the effects are really weird and hard to debug. Also, we want reproducible builds and obviously the above makes builds non-reproducible. So we have a FAQ entry that warns against using ccache and tells the user to clear the cache in case of problems. Now that ccache is called from the toolchain wrapper, it is in fact possible to at least use the 'mtime' compiler hash for the external toolchain and for the host-gcc. Indeed, in this case, the compiler executable comes from a tarball so the mtime will be a good reference for its state. Therefore, the patch (sed script) that changes the default from 'mtime' to 'none' is removed. For the internal toolchain, we can do better by providing a hash of the relevant toolchain options. We are only interested in things that affect the compiler itself, because ccache also processes the header files and it doesn't look at libraries because it doesn't cache the link step, just compilation. Everything that affects the compiler itself can nicely be summarised in $(HOST_GCC_FINAL_CONF_OPTS). Of course, also the compiler source itself is relevant, so the source tarball and all the patches are included in the hash. For this purpose, a new HOST_GCC_XTENSA_OVERLAY_TAR is introduced. The following procedure tests the ccache behaviour: Use this defconfig: BR2_arm=y BR2_CCACHE=y make readelf -A output/build/uclibc-1.0.6/libc/signal/signal.os -> Tag_CPU_name: "ARM926EJ-S" Now make menuconfig, change variant into BR2_cortex_a9 make clean; make readelf -A output/build/uclibc-1.0.6/libc/signal/signal.os -> Tag_CPU_name: "ARM926EJ-S" should be "Cortex-A9" After this commit, it is "Cortex-A9". Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Cc: Danomi Manchego Cc: Károly Kasza Cc: Samuel Martin Cc: Romain Naour Signed-off-by: Peter Korsgaard

package/ccache: bump to version 3.2.2

2015-06-04T13:28:22+00:00

Bump ccache to minor version 3.2.2. Also changed download URL to https. Signed-off-by: Karoly Kasza Signed-off-by: Peter Korsgaard