All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel: yocto: Add dependency on do_prepare_recipe_sysroot
Date: Wed, 22 Aug 2018 10:50:07 -0400	[thread overview]
Message-ID: <42c35010-9a50-d948-dc52-6607154111b4@windriver.com> (raw)
In-Reply-To: <20180822164757.34c36ac9@jawa>

On 08/22/2018 10:47 AM, Lukasz Majewski wrote:
> On Wed, 22 Aug 2018 10:44:08 -0400
> Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
> 
>> On 08/22/2018 10:20 AM, Lukasz Majewski wrote:
>>> On Wed, 22 Aug 2018 10:13:33 -0400
>>> Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
>>>    
>>>> On 08/22/2018 10:05 AM, Lukasz Majewski wrote:
>>>>> Hi Bruce,
>>>>>       
>>>>>> On 08/22/2018 09:40 AM, Lukasz Majewski wrote:
>>>>>>> Without this patch it happens that do_populate_recipe_sysroot is
>>>>>>> called just before do_compile (on multi core build machines).
>>>>>>> This is way too late as the .config generated in
>>>>>>> do_kernel_configme() is already broken.
>>>>>>>
>>>>>>> The problem is that do_kernel_configme() calls native's
>>>>>>> merge_config.sh script which may call bison and arm-linux-*-gcc
>>>>>>> to compile kconfig infrastructure to create base .config
>>>>>>> (scripts/kconfig/conf  --allnoconfig Kconfig.)
>>>>>>>
>>>>>>> It turns out that we only got above binaries after
>>>>>>> do_prepare_recipe_sysroot() is called.
>>>>>>> If those binaries are not available, the merge_config.sh do not
>>>>>>> generate base .config and without any error produces
>>>>>>> malfunctioned .config. The build process continues and as a
>>>>>>> result broken kernel is compiled.
>>>>>>>
>>>>>>> To reproduce:
>>>>>>>
>>>>>>> bitbake -c cleansstate virtual/kernel
>>>>>>> bitbake -c kernel_metadata -v virtual/kernel
>>>>>>> bitbake -c do_kernel_configme -v virtual/kernel
>>>>>>> (one shall see broken .config in ${B}/.config)
>>>>>>> bitbake -c do_populate_sysroot -v virtual/kernel
>>>>>>> bitbake -c do_compile -v virtual/kernel
>>>>>>>
>>>>>>> (Poky) SHA1: bb91b2ae3ee5cf108aa2f9b78abb14d5aa00831d
>>>>>>>
>>>>>>> Signed-off-by: Lukasz Majewski <lukma@denx.de>
>>>>>>> ---
>>>>>>>      meta/classes/kernel-yocto.bbclass | 1 +
>>>>>>>      1 file changed, 1 insertion(+)
>>>>>>>
>>>>>>> diff --git a/meta/classes/kernel-yocto.bbclass
>>>>>>> b/meta/classes/kernel-yocto.bbclass index 4ac3a39e47..19a3f2bc46
>>>>>>> 100644 --- a/meta/classes/kernel-yocto.bbclass
>>>>>>> +++ b/meta/classes/kernel-yocto.bbclass
>>>>>>> @@ -276,6 +276,7 @@ do_kernel_metadata[depends] =
>>>>>>> "kern-tools-native:do_populate_sysroot"
>>>>>>> do_validate_branches[depends] =
>>>>>>> "kern-tools-native:do_populate_sysroot" do_kernel_configme[dirs]
>>>>>>> += "${S} ${B}" +do_kernel_configme[depends] +=
>>>>>>> "virtual/kernel:do_prepare_recipe_sysroot"
>>>>>>
>>>>>> On a closer look .. what branch is this from ? We already have a
>>>>>> change that triggered breakage on 4.17+ that should fix this.
>>>>>>
>>>>>> i.e. commit ff1bdd75d50f0ebac3d599e461685ace29559a82 in oe-core,
>>>>>> adds:
>>>>>>
>>>>>> ----------
>>>>>>
>>>>>>      do_kernel_metadata[depends] =
>>>>>> "kern-tools-native:do_populate_sysroot"
>>>>>> do_validate_branches[depends] =
>>>>>> "kern-tools-native:do_populate_sysroot"
>>>>>>
>>>>>> +do_kernel_configme[depends] +=
>>>>>> "virtual/${TARGET_PREFIX}binutils:do_populate_sysroot"
>>>>>> +do_kernel_configme[depends] +=
>>>>>> "virtual/${TARGET_PREFIX}gcc:do_populate_sysroot"
>>>>>> +do_kernel_configme[depends] += "bc-native:do_populate_sysroot
>>>>>> bison-native:do_populate_sysroot"
>>>>>>      do_kernel_configme[dirs] += "${S} ${B}"
>>>>>>      do_kernel_configme() {
>>>>>>
>>>>>> ----------
>>>>>>
>>>>>> Which I don't see in the context of your patch.
>>>>>>      
>>>>>
>>>>> I do use poky as in the commit message.
>>>>
>>>> Yes, I checked that .. but that isn't a useful part of a patch
>>>> to oe-core.
>>>>
>>>> The kernel-yocto bbclass in that context is not the one in master,
>>>> and if I run a --contains on that commit ID, I don't get an active
>>>> branch.
>>>
>>> I might have misunderstood something... apparently.
>>>
>>> The changes which I did were to:
>>>
>>> poky/meta/classes/kernel-yocto.bbclass
>>>
>>> Is this a wrong place to add the fix?
>>
>> It is the right place to add the fix, but the tree that you are
>> using is not up to date with the current poky or oe-core master.
>>
>> There are other changes in place that address a similar failure.
>>
>> For us to look at this change, it needs to be rebased on top of
>> master (or master-next).
> 
> Now I got it. I shall sent the fix against cutting edge -master.
> 
> Shall I re-send the fix, of will you first check if patches in the
> queue doesn't fix it already?

I'll run the steps in your reproducer and let you know if it
works here.

Bruce

> 
>>
>> Bruce
>>
>>>    
>>>>
>>>> So the patch as it stands, cannot be applied to master (and I
>>>> also checked master-next in case something snuck in that I
>>>> missed) of oe-core or poky, so there's no way to work with it.
>>>>
>>>> Bruce
>>>>   
>>>>>
>>>>> Regarding the kernel - I do have my own recipe;
>>>>> inherit kernel
>>>>>
>>>>> require
>>>>> recipes-kernel/linux/linux-yocto.inc
>>>>>
>>>>>
>>>>> And then I do have:
>>>>> COMPATIBLE_MACHINE_display5 = "display5"
>>>>>
>>>>> KBUILD_DEFCONFIG_pn-linux-yocto-custom_display5 =
>>>>> "imx6q_display5_defconfig"
>>>>>
>>>>> As the board is in mainline I just point to Linus tree.
>>>>>       
>>>>>> Bruce
>>>>>>      
>>>>>>>      do_kernel_configme() {
>>>>>>>      	set +e
>>>>>>>      
>>>>>>>          
>>>>>>      
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Lukasz Majewski
>>>>>
>>>>> --
>>>>>
>>>>> DENX Software Engineering GmbH,      Managing Director: Wolfgang
>>>>> Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
>>>>> Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email:
>>>>> wd@denx.de
>>>>   
>>>
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Lukasz Majewski
>>>
>>> --
>>>
>>> DENX Software Engineering GmbH,      Managing Director: Wolfgang
>>> Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,
>>> Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email:
>>> wd@denx.de
>>
> 
> 
> 
> 
> Best regards,
> 
> Lukasz Majewski
> 
> --
> 
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> 



  reply	other threads:[~2018-08-22 14:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 13:40 [PATCH] kernel: yocto: Add dependency on do_prepare_recipe_sysroot Lukasz Majewski
2018-08-22 13:42 ` Bruce Ashfield
2018-08-22 13:51   ` Lukasz Majewski
2018-08-22 13:48 ` Bruce Ashfield
2018-08-22 14:05   ` Lukasz Majewski
2018-08-22 14:13     ` Bruce Ashfield
2018-08-22 14:20       ` Lukasz Majewski
2018-08-22 14:44         ` Bruce Ashfield
2018-08-22 14:47           ` Lukasz Majewski
2018-08-22 14:50             ` Bruce Ashfield [this message]
2018-08-23 16:45             ` Bruce Ashfield
2018-08-23 21:15               ` Lukasz Majewski
2018-08-22 14:07 ` ✗ patchtest: failure for " Patchwork

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=42c35010-9a50-d948-dc52-6607154111b4@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=lukma@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.