From: "André Draszik" <git@andred.net>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/6] kernel-yocto: streamline patch, configuration and audit phases
Date: Thu, 01 Sep 2016 17:14:15 +0100 [thread overview]
Message-ID: <1472746455.27417.57.camel@andred.net> (raw)
In-Reply-To: <81c8d462-9f65-cd7c-7dfe-f3acd2e21e18@windriver.com>
On Mi, 2016-08-31 at 16:17 -0400, Bruce Ashfield wrote:
> On 2016-08-31 4:54 AM, André Draszik wrote:
> >
> > On Di, 2016-08-30 at 14:35 -0400, Bruce Ashfield wrote:
> > >
> > > Can you clarify for me if you are are using SRC_URI items tagged with
> > > 'kmeta', i.e. a directory of fragments, or are you just adding
> > > .cfg/.scc
> > > items directly to the SRC_URI ?
> >
> > I do both:
> >
> > in the 1st layer, my kernel recipe boils down to:
> >
> > SRC_URI = "\
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> > stable.git;protocol=git;nocheckout=1;branch=${KBRANCH} \
> > file://0001-a-patch.patch \
> > file://kernel-meta;type=kmeta;destsuffix=${KMETA} \
> > "
> >
> > KERNEL_FEATURES_append = " patches/some-patches.scc"
> > KERNEL_FEATURES_append = " patches/more-patches.scc"
> > KERNEL_FEATURES_append = " patches/even-more-patches.scc"
> >
> > some of the above in turn include additional .scc items recursively.
> >
> >
> > In the 2nd layer, my .bbappend boils down to:
> >
> > FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}-4.4:"
> >
> > KERNEL_FEATURES_append_tgm = " patches/tgm.scc"
> >
> > 2nd-layer.scc is located in ${THISDIR}/kernel-meta/patches/ in the 2nd
> > layer. I don't specifically add another SRC_URI item tagged with 'kmeta'
> > (or
> > any other explicit SRC_URI item for that matter).
>
> One more clarification. From our problem description, are you saying
> that in your runs, only the meta data from layer2 is getting copied
> and not that from layer1 ?
That is what I had inferred from the error message:
| DEBUG: Executing shell function do_kernel_metadata
| ERROR. input file "patches/some-patches.scc" does not exist
| ERROR: could not process input files: <2nd_layer>/recipes-kernel/linux/linux-ramips-4.4/tgm/defconfig <1st_layer>/recipes-kernel/linux/linux-ramips-4.4/0001-a-patch.patch patches/some-patches.scc patches/more-patches.scc patches/even-more-patches.scc patches/tgm.scc
| See /tmp/tmp.mPP1jtatxm for details
| ERROR. input file "patches/some-patches.scc" does not exist
| ERROR: could not process input files: <2nd_layer>/recipes-kernel/linux/linux-ramips-4.4/tgm/defconfig <1st_layer>/recipes-kernel/linux/linux-ramips-4.4/0001-a-patch.patch patches/some-patches.scc patches/more-patches.scc patches/even-more-patches.scc patches/tgm.scc
| See /tmp/tmp.v9LU9ccpbl for details
| WARNING: exit code 1 from a shell command.
> I ran my sanity test, and saw meta data from both my layers copied ..
> so I'm worried that I misunderstood the issue you are seeing.
I can see that they are actually copied indeed, but it doesn't find them...
The file /tmp/tmp.v9LU9ccpbl mentioned above is empty.
> But looking at the code, I can definitely do some minor tweaks in this
> area .. I'm just trying to get the reproducer nailed down.
I can try to create one for you if you prefer tomorrow, rather than wasting
your time with this, if you don't get any further?
Andre'
next prev parent reply other threads:[~2016-09-01 16:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 18:26 [PATCH 0/6] kernel-yocto: consolidated pull request Bruce Ashfield
2016-08-15 18:26 ` [PATCH 1/6] linux-yocto/4.1: netfilter: x_tables: fix stable backport Bruce Ashfield
2016-08-15 18:26 ` [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29 Bruce Ashfield
2016-08-18 15:15 ` Richard Purdie
2016-08-18 15:16 ` Bruce Ashfield
2016-08-18 15:20 ` Richard Purdie
2016-08-19 14:57 ` Bruce Ashfield
2016-08-24 11:25 ` Richard Purdie
2016-08-24 13:14 ` Bruce Ashfield
2016-08-15 18:26 ` [PATCH 3/6] linux-yocto/4.1: config updates Bruce Ashfield
2016-08-15 18:26 ` [PATCH 4/6] linux-yocto/4.4: -rt update patch meta-data to remove () Bruce Ashfield
2016-08-15 18:26 ` [PATCH 5/6] kernel-yocto: streamline patch, configuration and audit phases Bruce Ashfield
2016-08-30 9:05 ` André Draszik
2016-08-30 13:05 ` Bruce Ashfield
2016-08-30 14:19 ` André Draszik
2016-08-30 18:35 ` Bruce Ashfield
2016-08-31 8:54 ` André Draszik
2016-08-31 20:17 ` Bruce Ashfield
2016-09-01 16:14 ` André Draszik [this message]
2016-09-01 20:21 ` Bruce Ashfield
2016-09-02 3:18 ` Bruce Ashfield
2016-09-02 4:37 ` Bruce Ashfield
2016-08-15 18:27 ` [PATCH 6/6] yocto-bsp/yocto-kernel: update to work with the latest kern-tools Bruce Ashfield
2016-08-16 16:00 ` [PATCH 0/6] kernel-yocto: consolidated pull request Burton, Ross
2016-08-16 16:01 ` Bruce Ashfield
2016-08-16 16:10 ` Burton, Ross
2016-08-16 16:11 ` Bruce Ashfield
2016-08-16 16:15 ` Burton, Ross
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=1472746455.27417.57.camel@andred.net \
--to=git@andred.net \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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