From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] kernel-devsrc: restructure for out of tree (and on target) module builds
Date: Thu, 1 Mar 2018 09:45:44 -0500 [thread overview]
Message-ID: <d55ef5a0-6bdb-ff5b-7d86-da087326146e@windriver.com> (raw)
In-Reply-To: <CAJTo0LaRS9yx+TisD3p5+HsK6mkr5wcFHkjZR9mAJXxgK5+HhA@mail.gmail.com>
On 2018-03-01 9:22 AM, Burton, Ross wrote:
> Swore I picked the v2 patch for the second run, I've fired a mini test
> build to see.
The other failures reported were valid and not addressed by v2. So only
32 bit ARM would have been fixed (packaging wise), the rest were ok.
I build and deployed kernel-devsrc for ARM multiple times, so if it does
actually fail again .. I'm *very* interested to hear.
Bruce
>
> Ross
>
> On 1 March 2018 at 13:59, Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>> wrote:
>
> On 2018-03-01 5:58 AM, Maxin B. John wrote:
>
>
> Also fails on musl:
>
> ERROR: Nothing RPROVIDES 'glibc-utils' (but
> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-musl/build/meta/recipes-kernel/linux/kernel-devsrc.bb
> <http://kernel-devsrc.bb> RDEPENDS on or otherwise requires it)
>
> Ross
>
> On 1 March 2018 at 08:28, Maxin B. John
> <maxin.john@intel.com <mailto:maxin.john@intel.com>> wrote:
>
>
> >On Wed, Feb 28, 2018 at 02:20:45PM -0500, Bruce Ashfield wrote:
> >> The existing kernel-devsrc package starts with a full copy
> of the kernel
> >> source and then starts to strip out elements that are not
> required.
> >>
> >> This results in extra time (I/O) and extra space being
> taken up in the
> >> final package. The main purpose of the kernel-devsrc
> package has been to
> >> build modules against the running kernel, not to include a
> full copy of
> >> the source code for re-building the kernel. The end result
> was a
> >> 600M kernel-devsrc package.
>
> Other failures are listed below:
> arm64:
> https://autobuilder.yocto.io/builders/nightly-arm64/builds/790/steps/Running%20Sanity%20Tests/logs/stdio
> <https://autobuilder.yocto.io/builders/nightly-arm64/builds/790/steps/Running%20Sanity%20Tests/logs/stdio>
>
> RESULTS - kernelmodule.KernelModuleTest.test_kernel_module -
> Testcase 1541: FAILED
>
> HOSTCC scripts/sortextable
> scripts/sortextable.c:31:10: fatal error:
> tools/be_byteshift.h: No such file or directory
> #include <tools/be_byteshift.h>
> ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[1]: *** [scripts/Makefile.host:102: scripts/sortextable]
> Error 1
> make: *** [Makefile:557: scripts] Error 2
> ----------------------------------------------------------------------
>
> Similar on qemuarm - poky-lsb :
>
> https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/812/steps/Running%20Sanity%20Tests/logs/stdio
> <https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/812/steps/Running%20Sanity%20Tests/logs/stdio>
>
> HOSTCC scripts/recordmcount
> HOSTCC scripts/sortextable
> scripts/sortextable.c:31:10: fatal error: tools/be_byteshift.h:
> No such file or directory
> #include <tools/be_byteshift.h>
> ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[1]: *** [scripts/Makefile.host:102:
> scripts/sortextable] Error 1
> make: *** [Makefile:557: scripts] Error 2
> -------------------------------------------------------------------------
>
> Also on PowerPC:
>
> https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/814/steps/Running%20Sanity%20Tests/logs/stdio
> <https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/814/steps/Running%20Sanity%20Tests/logs/stdio>
>
> scripts/sortextable.c:31:10: fatal error: tools/be_byteshift.h:
> No such file or directory
> #include <tools/be_byteshift.h>
> ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[1]: *** [scripts/Makefile.host:102: scripts/sortextable]
> Error 1
> make: *** [Makefile:557: scripts] Error 2
>
>
> I have all these fixed now.
>
> Will have a look at musl next.
>
> Cheers,
>
> Bruce
>
>
> Best Regards,
> Maxin
>
>
>
next prev parent reply other threads:[~2018-03-01 14:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 19:20 [PATCH v2] kernel-devsrc: restructure for out of tree (and on target) module builds 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2018-07-09 15:53 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
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
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=d55ef5a0-6bdb-ff5b-7d86-da087326146e@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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