summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/binutils/binutils-cross.inc
diff options
context:
space:
mode:
authorMark Hatle <mark.hatle@windriver.com>2010-09-29 15:18:01 -0500
committerRichard Purdie <rpurdie@linux.intel.com>2010-10-01 16:30:43 +0100
commit23f522e7a53821a8fb036e1aebddc7379d6f584e (patch)
treeb6fd962477f8b0c773275b6030e164bcd25aa43c /meta/recipes-devtools/binutils/binutils-cross.inc
parent9a1d4d0c8d8f995a12b341e44386d8d2c680f720 (diff)
downloadast2050-yocto-poky-23f522e7a53821a8fb036e1aebddc7379d6f584e.zip
ast2050-yocto-poky-23f522e7a53821a8fb036e1aebddc7379d6f584e.tar.gz
gcc: Update poisoned include path checking
[BUGID #374] The poison directory patch that was included with gcc-4.5.0 was not previously enabled due to the lack of the configure file changes. The patch has been updated to include the configure fragment. It was also noted that this patch preformed nearly the same functions as the zecke-no-host-includes patch, but with slightly different directories. The directories scanned were added from the zecke-no-host-includes patch to the new gcc-poison-dir-extend.patch. The other difference with the zecke patch is that poisoned headers is no longer an immediate fatal error. There may be instances where someone wants to do this. Adding -Werror=poison-system-directories to the CFLAGS would restore the behavior. Also fix a small problem where --help=warnings on gcc wouldn't return the poison-system-directories as a valid option, even though it was. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Diffstat (limited to 'meta/recipes-devtools/binutils/binutils-cross.inc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud