aboutsummaryrefslogtreecommitdiff
path: root/packages/gcc/12.2.0/0009-picolibc-Add-custom-spec-file-fragments-for-using-pi.patch
diff options
context:
space:
mode:
authorKeith Packard <keithp@keithp.com>2023-02-28 13:42:48 -0800
committerKeith Packard <keithp@keithp.com>2023-02-28 13:42:48 -0800
commit06a0160328f2234af739609fb8037f1b464764cb (patch)
tree40fd1345dd263071650f4fd7f166a1a25645c343 /packages/gcc/12.2.0/0009-picolibc-Add-custom-spec-file-fragments-for-using-pi.patch
parent287fccb8bcd0d06b5bb825c680c6b984f7b4728c (diff)
downloadcrosstool-ng-06a0160328f2234af739609fb8037f1b464764cb.tar.gz
crosstool-ng-06a0160328f2234af739609fb8037f1b464764cb.tar.bz2
crosstool-ng-06a0160328f2234af739609fb8037f1b464764cb.zip
packages/gcc: Add gcc patch to allow getenv default values
This patch, submitted upstream but not (yet?) accepted, adds a third parameter to the specs file 'getenv' function that provides a value for when the environment variable is not set, instead of having gcc fail. This seemed like the safest way to provide a mechanism for getting the installed location of the toolchain from inside a specs file as, when not installed in the built-in location, gcc already sets the GCC_EXEC_PREFIX environment variable to a well defined location within that directory hierarchy, but when installed in the location specified at compile time, gcc does not. Providing a default value that matches the compile-time location then allows the specs file to compute paths relative to the current GCC installation location, whereever it is installed. Signed-off-by: Keith Packard <keithp@keithp.com>
Diffstat (limited to 'packages/gcc/12.2.0/0009-picolibc-Add-custom-spec-file-fragments-for-using-pi.patch')
0 files changed, 0 insertions, 0 deletions