From 3f4f580954fd90ce3ad6eb6ca6ab7b96eb66539c Mon Sep 17 00:00:00 2001 From: Kevin Darbyshire-Bryant Date: Tue, 22 Aug 2017 11:01:07 +0100 Subject: toolchain: gcc: update 7.x to 7.2.0 Bump gcc from 7.1 to 7.2 Compile & run tested: ar71xx Trace history of current patches and update with commit ref & comment to give more clue as to why they're still around/needed. Some have changed form since the original commit but some clue is better than no clue at all. Signed-off-by: Kevin Darbyshire-Bryant Tested-by: Koen Vandeputte --- .../patches/7.2.0/920-specs_nonfatal_getenv.patch | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 toolchain/gcc/patches/7.2.0/920-specs_nonfatal_getenv.patch (limited to 'toolchain/gcc/patches/7.2.0/920-specs_nonfatal_getenv.patch') diff --git a/toolchain/gcc/patches/7.2.0/920-specs_nonfatal_getenv.patch b/toolchain/gcc/patches/7.2.0/920-specs_nonfatal_getenv.patch new file mode 100644 index 0000000..69b4062 --- /dev/null +++ b/toolchain/gcc/patches/7.2.0/920-specs_nonfatal_getenv.patch @@ -0,0 +1,22 @@ +Author: Jo-Philipp Wich +Date: Sat Apr 21 03:02:39 2012 +0000 + + gcc: add patch to make the getenv() spec function nonfatal if requested environment variable is unset + + SVN-Revision: 31390 + +--- a/gcc/gcc.c ++++ b/gcc/gcc.c +@@ -9280,8 +9280,10 @@ getenv_spec_function (int argc, const ch + value = varname; + + if (!value) +- fatal_error (input_location, +- "environment variable %qs not defined", varname); ++ { ++ warning (input_location, "environment variable %qs not defined", varname); ++ value = ""; ++ } + + /* We have to escape every character of the environment variable so + they are not interpreted as active spec characters. A -- cgit v1.1