From: Bruce Ashfield <bruce.ashfi...@xilinx.com>

To support on-target module building, we need to include syscall.tbl
for ARM64 (just like we do for other architectures).

We also copy .config with -a to ensure that we don't trigger extra
processing and regen configs.

Signed-off-by: Bruce Ashfield <bruce.ashfi...@xilinx.com>
Signed-off-by: Bruce Ashfield <bruce.ashfi...@gmail.com>
---
 meta/recipes-kernel/linux/kernel-devsrc.bb | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb 
b/meta/recipes-kernel/linux/kernel-devsrc.bb
index b6f2dbc2b0..2fa4be67cc 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -78,7 +78,7 @@ do_install() {
            cp Module.markers $kerneldir/build
        fi
 
-       cp .config $kerneldir/build
+       cp -a .config $kerneldir/build
 
        # This scripts copy blow up QA, so for now, we require a more
        # complex 'make scripts' to restore these, versus copying them
@@ -128,11 +128,12 @@ do_install() {
 
            # extra files, just in case
            cp -a --parents tools/objtool/* $kerneldir/build/
-           cp -a --parents tools/lib/str_error_r.c $kerneldir/build/
-           cp -a --parents tools/lib/string.c $kerneldir/build/
+           cp -a --parents tools/lib/* $kerneldir/build/
            cp -a --parents tools/lib/subcmd/* $kerneldir/build/
 
            cp -a --parents tools/include/* $kerneldir/build/
+
+           cp -a --parents $(find tools/arch/${ARCH}/ -type f) 
$kerneldir/build/
        fi
 
        if [ "${ARCH}" = "arm64" ]; then
@@ -186,6 +187,7 @@ do_install() {
 
        # required for generate missing syscalls prepare phase
        cp -a --parents $(find arch/x86 -type f -name "syscall_32.tbl") 
$kerneldir/build
+       cp -a --parents $(find arch/arm -type f -name "*.tbl") $kerneldir/build
 
        if [ "${ARCH}" = "x86" ]; then
            # files for 'make prepare' to succeed with kernel-devel
-- 
2.19.1

-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to