gcc-target: Fix libatomic dependency tracking issues
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 22 Sep 2013 10:48:28 +0000 (10:48 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 22 Sep 2013 11:19:43 +0000 (12:19 +0100)
commit8bf1126a4633e8086f608df4a02f4caa4582dd81
treeea3c6c75bf8555c03ef6d5b0c7c35957cd3264fa
parenta3e2a39f58c3499154814137e1719da14a9c4489
gcc-target: Fix libatomic dependency tracking issues

The --enable-dependency-tracking option was added to workaround build
issues in libatomic. This fixes that build problem properly and removes
the flag since the dependency tracking code appears to be full of races
which are much deeper and harder to fix.

As per the automake manual, dependency tracking is only useful and worth
the build performance cost if you are doing more than one compile of the same
source code which in most cases we are not so this is a good thing anyway.

(From OE-Core rev: a3b665a80abed4c0659925e1cceb1568af023711)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/gcc/gcc-4.8.inc
meta/recipes-devtools/gcc/gcc-4.8/0046-libatomic-deptracking.patch [new file with mode: 0644]
meta/recipes-devtools/gcc/gcc-target.inc