[oe-commits] Paul Barker : kernel.bbclass: Complete fix for modules symlink
git at git.openembedded.org
git at git.openembedded.org
Fri May 29 13:55:20 UTC 2015
Module: openembedded-core.git
Branch: dylan
Commit: f07a4e0d80f5e0dd94514f6aae11a7bd56034f30
URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=f07a4e0d80f5e0dd94514f6aae11a7bd56034f30
Author: Paul Barker <paul.barker at commagility.com>
Date: Tue May 5 18:33:01 2015 +0100
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 <paul.barker at commagility.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
meta/classes/kernel.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 324e812..67b662a 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}
More information about the Openembedded-commits
mailing list