aboutsummaryrefslogtreecommitdiffstats
path: root/meta-initramfs/recipes-kernel/linux
diff options
context:
space:
mode:
authorRobert Yang <liezhi.yang@windriver.com>2014-04-03 22:08:22 +0800
committerPaul Eggleton <paul.eggleton@linux.intel.com>2014-04-06 13:31:23 +0100
commit4b2a4dac0f19f1ba8a33b35b05be0808eca91b08 (patch)
tree593bb3d4ac601e3c2fa9b8bb006be249b82af786 /meta-initramfs/recipes-kernel/linux
parenta60bf8c73adecf68d048c7725773d0772b22873e (diff)
downloadmeta-openembedded-contrib-4b2a4dac0f19f1ba8a33b35b05be0808eca91b08.tar.gz
meta-openembedded-contrib-4b2a4dac0f19f1ba8a33b35b05be0808eca91b08.tar.bz2
meta-openembedded-contrib-4b2a4dac0f19f1ba8a33b35b05be0808eca91b08.zip
cherokee: only install configured.py once
Both the two rules install-adminpyDATA and install-generatedDATA will install the configured.py to the same location, they can run parallel, and they use "install -m", which would might build failures: /usr/bin/install: setting permissions for `/path/to/configured.py': No such file or directory This is because the first install is setting the permission while the second install is removing the file an re-install. Only install the configured.py once will fix the problem, I think that there is no side effect since it installed the same file to the same location twice in the past. Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Diffstat (limited to 'meta-initramfs/recipes-kernel/linux')
0 files changed, 0 insertions, 0 deletions