aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/generic
diff options
context:
space:
mode:
authorMichael Pratt <mcpratt@pm.me>2023-05-25 02:31:52 -0400
committerPetr Štetiar <ynezz@true.cz>2023-06-05 08:31:48 +0200
commit665fe2f818300f0b84c8c458fc49ae58ff8853aa (patch)
treecf737883e913fdf874093f203585becb592971b3 /target/linux/generic
parentd87a8aa148ddf93b199a759deb088fff73787025 (diff)
downloadupstream-665fe2f818300f0b84c8c458fc49ae58ff8853aa.tar.gz
upstream-665fe2f818300f0b84c8c458fc49ae58ff8853aa.tar.bz2
upstream-665fe2f818300f0b84c8c458fc49ae58ff8853aa.zip
prereq-build: fix inconsistent value of $PATH
In the recipe SetupHostCommand for checking and creating symlinks, $PATH was only overridden for one of several commands. This causes the symlinks to be included in the paths to pick a program from when the check was repeated, because staging_dir/host/bin was included in $PATH, but only *sometimes*. When the check ran again, the command succeded with a $PATH including the symlink, (eval "$$$$$$$$cmd") while the path to the program was evaluated with a $PATH NOT including the symlink, (bin=...) causing the symlink to be relinked incorrectly, instead of passing as exactly the same. Coincidentally, this was only a problem if the symlink targeted the alternative program with a different name. By overriding the value of $PATH at the invocation of Make, it will apply to the entire environment of the checks. Signed-off-by: Michael Pratt <mcpratt@pm.me>
Diffstat (limited to 'target/linux/generic')
0 files changed, 0 insertions, 0 deletions