Re: [yocto] Debugging a build issue in an isolated enviroment

Opa! Great command for the future, tnx. Strange that it isn't listed here and is greppable in bitbake -e u-boot-fw-utils-senic... Here it is: u-boot-fw-utils-senic-v2017.03+git999-r0 do_listtasks: do_build Default task for a recipe - depends on all other normal tasks required to

Re: [yocto] Debugging a build issue in an isolated enviroment

On 2 November 2017 at 13:31, Alan Martinovic wrote: > Found what I was asking for with: > > bitbake -e > > going through the output, there are mentions of patch_do_patch(). > I've traced it to meta/classes/patch.bbclass. > > However, trying to execute just the

Re: [yocto] Debugging a build issue in an isolated enviroment

Found what I was asking for with: bitbake -e going through the output, there are mentions of patch_do_patch(). I've traced it to meta/classes/patch.bbclass. However, trying to execute just the patching for the recipe doesn't work. build⟫ bitbake -c patch u-boot-fw-utils-senic ... ERROR: Task

Re: [yocto] Debugging a build issue in an isolated enviroment

That I can't see the changes for that particular patch in the source (by manually checking the source for the changes). Other patches are applied correctly, I can trace them in the sources. I have no "temp/log.do_patch" and find notions of patches (both the successfully and unsuccessfully applied

Re: [yocto] Debugging a build issue in an isolated enviroment

What do you mean by patches not being applied correctly? temp/log.do_patch has the output from patch so that might show that you've a patch that applies with lots of fuzz and is applied incorrectly. Ross On 2 November 2017 at 11:46, Alan Martinovic wrote: > I see,

Re: [yocto] Debugging a build issue in an isolated enviroment

I see, so I can't use the devshell to debug why the patch hasn't been correctly applied. The answer you gave help for debugging actual build and configure problems. Debugging patching seems to be out scope for this thread. Will start a new one. On Thu, Nov 2, 2017 at 12:13 PM, Burton, Ross

Re: [yocto] Debugging a build issue in an isolated enviroment

The patching is done by a bbclass (patch.bbclass) and helper modules (meta/oe/lib/patch.py), so you can't execute it like a shell task (such as do_compile). Ross On 2 November 2017 at 11:05, Alan Martinovic wrote: > Thanks for the suggestions > Am currently

Re: [yocto] Debugging a build issue in an isolated enviroment

Thanks for the suggestions Am currently implementing both of them and am trying to understand how the patching is done. In the temp directory I can see all the tasks. For some reasons the patch wasn't applied correctly and I'm debugging why. I have patches from before which are being correctly

Re: [yocto] Debugging a build issue in an isolated enviroment

On 1 November 2017 at 17:38, Alan Martinovic wrote: > I'm just upgrading to pyro and have some issues with u-boot-fw-utils. > > The error fails at do_compile stage which looks like this: > > do_compile () { > oe_runmake ${UBOOT_MACHINE} >

Re: [yocto] Debugging a build issue in an isolated enviroment

On 1 November 2017 at 17:38, Alan Martinovic wrote: > Is there a way to run the above listed make command with the same > environment as it is run when the error is produced? > $ bitbake -c devshell This drops you in a new terminal with the same environment that

[yocto] Debugging a build issue in an isolated enviroment

I'm just upgrading to pyro and have some issues with u-boot-fw-utils. The error fails at do_compile stage which looks like this: do_compile () { oe_runmake ${UBOOT_MACHINE} oe_runmake env } The error is: Log data follows: | DEBUG: Executing shell function