From f07a4e0d80f5e0dd94514f6aae11a7bd56034f30 Mon Sep 17 00:00:00 2001 From: Paul Barker Date: Tue, 5 May 2015 18:33:01 +0100 Subject: kernel.bbclass: Complete fix for modules symlink 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. Signed-off-by: Paul Barker Signed-off-by: Richard Purdie --- meta/classes/kernel.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta') 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() { if [ ${MODULE_TARBALL_DEPLOY} = "1" ] && (grep -q -i -e '^CONFIG_MODULES=y$' .config); then mkdir -p ${D}/lib tar -cvzf ${DEPLOYDIR}/${MODULE_TARBALL_BASE_NAME} -C ${D} lib - ln -sf ${MODULE_TARBALL_BASE_NAME} ${MODULE_TARBALL_SYMLINK_NAME} + ln -sf ${MODULE_TARBALL_BASE_NAME} ${DEPLOYDIR}/${MODULE_TARBALL_SYMLINK_NAME} fi cd ${DEPLOYDIR} -- cgit 1.2.3-korg