summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Barker <paul.barker@commagility.com>2015-05-05 18:33:01 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-05-29 14:54:57 +0100
commit0fcfdc4d54dbe617777a9cf76b72213f908f8a6e (patch)
treed12e48160ab2d6a635aa8dfac3a3d5f16df7ba6c
parenta04380fd0f8f86c47e31376410182b52a670ea41 (diff)
downloadpoky-dylan.tar.gz
kernel.bbclass: Complete fix for modules symlinkdylan
The fix backported in commit aa9fc551 of oe-core does not completely fix the issue (Yocto #4595) as intended. The modules symlink is still created in the working directory instead of in the deploy directory. To fix this, we just need to use an absolute path to ${DEPLOYDIR} when creating the symlink. (From OE-Core rev: f07a4e0d80f5e0dd94514f6aae11a7bd56034f30) Signed-off-by: Paul Barker <paul.barker@commagility.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/classes/kernel.bbclass2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 324e8120b9..67b662ac08 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -372,7 +372,7 @@ kernel_do_deploy() {
372 if [ ${MODULE_TARBALL_DEPLOY} = "1" ] && (grep -q -i -e '^CONFIG_MODULES=y$' .config); then 372 if [ ${MODULE_TARBALL_DEPLOY} = "1" ] && (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
373 mkdir -p ${D}/lib 373 mkdir -p ${D}/lib
374 tar -cvzf ${DEPLOYDIR}/${MODULE_TARBALL_BASE_NAME} -C ${D} lib 374 tar -cvzf ${DEPLOYDIR}/${MODULE_TARBALL_BASE_NAME} -C ${D} lib
375 ln -sf ${MODULE_TARBALL_BASE_NAME} ${MODULE_TARBALL_SYMLINK_NAME} 375 ln -sf ${MODULE_TARBALL_BASE_NAME} ${DEPLOYDIR}/${MODULE_TARBALL_SYMLINK_NAME}
376 fi 376 fi
377 377
378 cd ${DEPLOYDIR} 378 cd ${DEPLOYDIR}