|author||Thomas Petazzoni <email@example.com>||2014-12-10 23:53:57 +0100|
|committer||Thomas Petazzoni <firstname.lastname@example.org>||2014-12-11 00:05:52 +0100|
Add option for paranoid unsafe path checking
This commit adds a Config.in option to the "Build options" submenu to enable paranoid checking of unsafe paths. This mechanism is added as an option so that when we'll enable it in the autobuilders, people trying to reproduce the build failures will be able to do so by just downloading the configuration file. If instead we were leaving this feature as an environment variable, everyone would have to remember to pass this environment variable to reproduce build issues. And certain build issues triggered by paranoid unsafe patch checking may not be visible in the build output, for example when they happen during the execution of configure scripts. Since this option is fairly advanced, a new submenu inside "Build options" is created, for Advanced options. Signed-off-by: Thomas Petazzoni <email@example.com> Acked-by: "Yann E. MORIN" <firstname.lastname@example.org> Reviewed-by: Romain Naour <email@example.com> Tested-by: Romain Naour <firstname.lastname@example.org>
Diffstat (limited to 'Config.in')
1 files changed, 20 insertions, 0 deletions
@@ -569,6 +569,26 @@ config BR2_GLOBAL_PATCH_DIR
Otherwise, if the directory <global-patch-dir>/<packagename> exists,
then all *.patch files in the directory will be applied.
+ bool "paranoid check of library/header paths"
+ By default, when this option is disabled, when the Buildroot
+ cross-compiler will encounter an unsafe library or header
+ path (such as /usr/include, or /usr/lib), the compiler will
+ display a warning.
+ By enabling this option, this warning is turned into an
+ error, which will completely abort the build when such
+ unsafe paths are encountered.
+ Note that this mechanism is available for both the internal
+ toolchain (through gcc and binutils patches) and external
+ toolchain backends (through the external toolchain wrapper).