From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] kernel-devsrc: restructure for out of tree (and on target) module builds
Date: Tue, 10 Jul 2018 22:34:10 -0400 [thread overview]
Message-ID: <97d70868-7ee5-01a7-7898-2713de76dbcd@windriver.com> (raw)
In-Reply-To: <c0baf80e5943135f4f65a93d849ee68419065c45.camel@linuxfoundation.org>
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
>
next prev parent reply other threads:[~2018-07-11 2:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 15:53 [PATCH v2] kernel-devsrc: restructure for out of tree (and on target) module builds Bruce Ashfield
2018-07-10 10:21 ` Richard Purdie
2018-07-10 13:09 ` Bruce Ashfield
2018-07-10 16:38 ` Bruce Ashfield
2018-07-10 21:41 ` Richard Purdie
2018-07-11 2:34 ` Bruce Ashfield [this message]
2018-07-12 13:49 ` Bruce Ashfield
2018-07-12 13:53 ` Richard Purdie
2018-07-12 13:55 ` Bruce Ashfield
2018-07-12 17:02 ` Khem Raj
2018-07-12 17:07 ` Bruce Ashfield
2018-07-12 17:22 ` Khem Raj
2018-07-12 17:26 ` Bruce Ashfield
2018-07-26 14:04 ` Bruce Ashfield
2018-07-26 14:17 ` richard.purdie
2018-07-26 17:01 ` Richard Purdie
2018-07-30 22:26 ` richard.purdie
2018-07-31 1:07 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2018-02-28 19:20 Bruce Ashfield
2018-02-28 21:10 ` Mark Hatle
2018-02-28 21:12 ` Bruce Ashfield
2018-03-01 8:28 ` Maxin B. John
2018-03-01 9:37 ` Burton, Ross
2018-03-01 10:58 ` Maxin B. John
2018-03-01 12:58 ` Bruce Ashfield
2018-03-01 13:59 ` Bruce Ashfield
2018-03-01 14:22 ` Burton, Ross
2018-03-01 14:45 ` Bruce Ashfield
2018-03-01 14:57 ` Burton, Ross
2018-03-02 14:23 ` Bruce Ashfield
2018-03-02 14:26 ` Burton, Ross
2018-03-02 15:20 ` Khem Raj
2018-03-02 18:16 ` Khem Raj
2018-03-02 19:29 ` Bruce Ashfield
2018-03-02 23:14 ` Burton, Ross
2018-03-01 12:57 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97d70868-7ee5-01a7-7898-2713de76dbcd@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox