diff options
author | 2016-09-21 22:52:49 +0200 | |
---|---|---|
committer | 2016-09-21 22:53:28 +0200 | |
commit | b1001acaf08da9d203953a5b4c3dee68e3c0d537 (patch) | |
tree | 2a2a149ff0fd03c05c86a84af3156a045a69f1d5 | |
parent | dcd36d47d2416e1c713849a8b95fa5e6e8530b51 (diff) | |
download | buildroot-2016.08.x.tar.gz buildroot-2016.08.x.tar.bz2 |
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
-rw-r--r-- | CHANGES | 25 | ||||
-rw-r--r-- | Makefile | 2 |
2 files changed, 26 insertions, 1 deletions
@@ -1,3 +1,28 @@ +2016.08.1, Released September 21st, 2016 + + Fix potential entire root filesystem removal in the external + toolchain handling. This would trigger if (and only if) the + following conditions are met: + + - The user has selected a "known toolchain profile", such as a + Linaro toolchain, a Sourcery CodeBench toolchain etc. People + using "custom toolchain profile" are not affected. + + - The user has enabled BR2_TOOLCHAIN_EXTERNAL_PREINSTALLED=y + to indicate that the toolchain is already locally available + (as opposed to having Buildroot download and extract the + toolchain) + + - The user has left BR2_TOOLCHAIN_EXTERNAL_PATH empty, because + his toolchain is directly available through the PATH + environment variable. When BR2_TOOLCHAIN_EXTERNAL_PATH is + non-empty, Buildroot will do something silly (remove the + toolchain contents), but that are limited to the toolchain + itself. + + When such conditions are met, Buildroot will run "rm -rf /*" + due to TOOLCHAIN_EXTERNAL_INSTALL_DIR being empty. + 2016.08, Released Septermber 1st, 2016 Minor fixes. @@ -46,7 +46,7 @@ else # umask all: # Set and export the version string -export BR2_VERSION := 2016.08 +export BR2_VERSION := 2016.08.1 # Save running make version since it's clobbered by the make package RUNNING_MAKE_VERSION := $(MAKE_VERSION) |