[Buildroot] [for-next: PATCH 1/2] toolchain: enable paranoid unsafe path check by default

[Buildroot] [for-next: PATCH 1/2] toolchain: enable paranoid unsafe path check by default

[Romain Naour]

This check is enabled for all build in the Buildroot autobuilders since [1]
(i.e since 2015.02 release).

Enable this option by default.

[1] https://git.busybox.net/buildroot-test/commit/?id=41552e2a249de4568aa01f14bd588d1c8166f70b

Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
 Config.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Config.in b/Config.in
index b5cc892..93b4f69 100644
--- a/Config.in
+++ b/Config.in
@@ -683,6 +683,7 @@ menu "Advanced"
 
 config BR2_COMPILER_PARANOID_UNSAFE_PATH
 	bool "paranoid check of library/header paths"
+	default y
 	help
 	  By default, when this option is disabled, when the Buildroot
 	  cross-compiler will encounter an unsafe library or header
-- 
2.5.5

[Buildroot] [for-next: PATCH 2/2] toolchain: update paranoid unsafe path comment

[Romain Naour]

Since 919c06c28295f19ca49459b98d8954148b381360 the calls to gcc always pass
through the toolchain wrapper and all gcc patches to support poisoning has been
removed.

Update the BR2_COMPILER_PARANOID_UNSAFE_PATH comment.

Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
 Config.in | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Config.in b/Config.in
index 93b4f69..849d7f5 100644
--- a/Config.in
+++ b/Config.in
@@ -695,8 +695,8 @@ config BR2_COMPILER_PARANOID_UNSAFE_PATH
 	  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).
+	  toolchain (through the toolchain wrapper and binutils patches)
+	  and external toolchain backends (through the toolchain wrapper).
 
 endmenu
 
-- 
2.5.5

[Buildroot] [for-next: PATCH 2/2] toolchain: update paranoid unsafe path comment

[Thomas Petazzoni]

Hello,

On Sun, 15 May 2016 12:26:01 +0200, Romain Naour wrote:
> Since 919c06c28295f19ca49459b98d8954148b381360 the calls to gcc always pass
> through the toolchain wrapper and all gcc patches to support poisoning has been
> removed.
> 
> Update the BR2_COMPILER_PARANOID_UNSAFE_PATH comment.
> 
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
>  Config.in | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

I know you labeled this patch as being "for next", but I believe it
really should be applied to master, so that's what I've done.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [for-next: PATCH 1/2] toolchain: enable paranoid unsafe path check by default

[Thomas Petazzoni]

Hello,

On Sun, 15 May 2016 12:26:00 +0200, Romain Naour wrote:
> This check is enabled for all build in the Buildroot autobuilders since [1]
> (i.e since 2015.02 release).
> 
> Enable this option by default.
> 
> [1] https://git.busybox.net/buildroot-test/commit/?id=41552e2a249de4568aa01f14bd588d1c8166f70b
> 
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
>  Config.in | 1 +
>  1 file changed, 1 insertion(+)

Applied to next, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com