summaryrefslogtreecommitdiffstats
path: root/package/python-daemon/python-daemon.mk
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2016-08-29 17:53:58 +0200
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2016-09-18 16:07:35 +0200
commit105a8c156c4818f121169996f5fbe6ebd46e0068 (patch)
tree396f8577885fe49d44d96d9c877fd2aef45e32a8 /package/python-daemon/python-daemon.mk
parent01e807f0d8dd411643e4f0939a5b8623bfbe9518 (diff)
downloadbuildroot-105a8c156c4818f121169996f5fbe6ebd46e0068.tar.gz
buildroot-105a8c156c4818f121169996f5fbe6ebd46e0068.zip
toolchain/wrapper: display options leading to a paranoid failure
Current, we only display the path that causes the paranoid failure. This is sufficient, as we can fail only for -I and -L options, and it is thus easy to infer from the path, which option is the culprit. However, we're soon to add a new test for the -isystem option, and then when a failure occurs, we would not know whether it was because of -I or -isystem. Being able to differentiate both can be hugely useful to track down the root cause for the unsafe path. Add two new arguments to the check_unsafe_path() function: one with the current-or-previous argument, one to specify whether it has the path in it or not. Print that in the error message, instead of just the path. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/python-daemon/python-daemon.mk')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud