gcc: remove unsafe patch check (poison system dirs) patch
authorArnout Vandecappelle <arnout@mind.be>
Sun, 4 Oct 2015 12:28:43 +0000 (13:28 +0100)
committerPeter Korsgaard <peter@korsgaard.com>
Sun, 4 Oct 2015 16:22:20 +0000 (18:22 +0200)
commit2f8dc29c1d9f2adda850dead5325e422715d251e
tree6ab9ce613902d0219296c298fed38c73825e9781
parent919c06c28295f19ca49459b98d8954148b381360
gcc: remove unsafe patch check (poison system dirs) patch

Now that the calls to gcc always pass through the toolchain wrapper, it
is no longer necessary to patch gcc to support poisoning.

This does have the disadvantage that there is no unsafe path check for
libc, libgcc and libstdc++ (all of these are built before the wrapper
exists). But we can assume that the toolchain components themselves
should be pretty safe.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Reviewed-by: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
package/gcc/4.7.4/910-gcc-poison-system-directories.patch [deleted file]
package/gcc/4.8.5/910-gcc-poison-system-directories.patch [deleted file]
package/gcc/4.9.3/910-gcc-poison-system-directories.patch [deleted file]
package/gcc/5.2.0/200-gcc-poison-system-directories.patch [deleted file]
package/gcc/arc-2015.06/910-gcc-poison-system-directories.patch [deleted file]
package/gcc/gcc-final/gcc-final.mk