On 2018-07-10 5:41 PM, Richard Purdie wrote:
On Tue, 2018-07-10 at 12:38 -0400, Bruce Ashfield wrote:
On 07/10/2018 06:21 AM, Richard Purdie wrote:
On Mon, 2018-07-09 at 11:53 -0400, Bruce Ashfield wrote:
I'll try the other configs, but clearly I have something different in
my x86-64 build.
I can't run the self tests directly, but am copying the files onto my
qemu session and running things myself:
root@qemux86-64:/lib/modules/4.14.48-yocto-standard/build# make
ARCH=x86
scripts prepare
Makefile:950: "Cannot use CONFIG_STACK_VALIDATION=y, please install
libelf-dev, libelf-devel or elfutils-libelf-devel"
CHK scripts/mod/devicetable-offsets.h
SYSTBL arch/x86/include/generated/asm/syscalls_32.h
SYSHDR arch/x86/include/generated/asm/unistd_32_ia32.h
SYSHDR arch/x86/include/generated/asm/unistd_64_x32.h
SYSTBL arch/x86/include/generated/asm/syscalls_64.h
SYSHDR arch/x86/include/generated/uapi/asm/unistd_32.h
SYSHDR arch/x86/include/generated/uapi/asm/unistd_64.h
SYSHDR arch/x86/include/generated/uapi/asm/unistd_x32.h
HOSTCC arch/x86/tools/relocs_32.o
HOSTCC arch/x86/tools/relocs_64.o
HOSTCC arch/x86/tools/relocs_common.o
HOSTLD arch/x86/tools/relocs
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
Makefile:950: "Cannot use CONFIG_STACK_VALIDATION=y, please install
libelf-dev, libelf-devel or elfutils-libelf-devel"
root@qemux86-64:/tmp# make
make -C /usr/src/kernel M=/tmp modules
make[1]: Entering directory '/lib/modules/4.14.48-yocto-
standard/build'
Makefile:950: "Cannot use CONFIG_STACK_VALIDATION=y, please install
libelf-dev, libelf-devel or elfutils-libelf-devel"
Building modules, stage 2.
MODPOST 1 modules
make[1]: Leaving directory '/lib/modules/4.14.48-yocto-
standard/build'
root@qemux86-64:/tmp# insmod hellomod.ko
[ 419.211616] hellomod: loading out-of-tree module taints kernel.
[ 419.212586] Hello world!
This is on the core-image-kernel-dev image, which is the one that
I created to test all this.
What image is that using ? some sato sdk one ?
We really need to find you a way to run these. The problem is the qemu
graphics piece? You can't have a dummy vncserver or something to direct
them at?
My config never seems to build and run the tests that I need, I had
it work once, and then never again. So I prefer to just build, boot
and run tests manually.
Regardless of the automation, I can easily do "make scripts prepare"
on the kernel-devsrc package, so that is extremely odd that it doesn't
work with that image. I'll try and add devsrc to a sato build and see
of objtool goes nuts.
I'm also unable to build lttng-modules for mips at the moment, so at
least mips is untestable for me.
Bruce
The image is a core-image-sato-sdk...
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
