summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/valgrind/valgrind-3.6.1
diff options
context:
space:
mode:
authorMark Hatle <mark.hatle@windriver.com>2011-06-21 23:56:25 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-06-30 20:46:34 +0100
commit0cfa7ebcf661aa0645c6d4d858b04946ebacb7e4 (patch)
tree38957f48c6aee97271a6494fb7fd1d192e700767 /meta/recipes-devtools/valgrind/valgrind-3.6.1
parentdb6a4e07f3a35163c751996ca3ac86b6bf5650e9 (diff)
downloadopenembedded-core-0cfa7ebcf661aa0645c6d4d858b04946ebacb7e4.tar.gz
openembedded-core-0cfa7ebcf661aa0645c6d4d858b04946ebacb7e4.tar.bz2
openembedded-core-0cfa7ebcf661aa0645c6d4d858b04946ebacb7e4.tar.xz
openembedded-core-0cfa7ebcf661aa0645c6d4d858b04946ebacb7e4.zip
Add umask task control
Bitbake now allows the umask to be specified per task. The following tasks will have a umask of 022 set by default: do_configure do_compile do_install do_package do_populate_sysroot do_rootfs do_configure and do_compile need a umask of 022 set because -many- recipes directly copy generated files out of recipe's build directory. Instead of fixing each existing and future recipe, it was shown to be much easier to just set the umask. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Diffstat (limited to 'meta/recipes-devtools/valgrind/valgrind-3.6.1')
0 files changed, 0 insertions, 0 deletions