openembedded-core.git/meta/classes/kernel-yocto.bbclass, branch pyro

kernel-yocto/kern-tools: fix do_validate_branches clean stage

2017-04-28T10:26:05+00:00

It was reported that do_validate_branches was failing with the following
error:

  Log data follows:
  | DEBUG: Executing shell function do_validate_branches
  | HEAD is now at fe0fb8d Merge tag 'v4.10.9' into standard/base
  | mkdir: cannot create directory .: File exists
  |
  | [ERROR] Can't find patch dir at ./patches/standard/base
  | usage: kgit s2q
  | WARNING: exit code 1 from a shell command.
  | ERROR: Function failed: do_validate_branches

This was triggered by the execution of 'kgit-s2q --clean' after forcing
the SRCREV to something other than the tip of the branch. --clean is
being run to remove any sentinel files from previous kernel builds to
ensure that the tree is in a consistent state.

There were two bugs, --clean was being executed and not exiting the
script as it was supposed to. Hence validation for applying patches
was done, and threw the error that eventually makes it to the console.

And the second bug is that since do_validate_branches actually calls
kgit-s2q --clean, the dependency on kern-tools-native needs to be on
that function (versus do_kernel_metadata which runs later).

With the tweaked kern-tool + the dependency fix, we no longer see this
error.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

kernel-yocto: trivial: remove extra } from bsp_definition

2017-02-19T14:16:51+00:00

A typo introduced an extra } in the logging of the bsp_definition.
While this won't cause problems .. it needs to be fixed!

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

kernel-yocto.bbclass: ensure repatching when HEAD is checked out

2017-02-19T14:16:50+00:00

In some cases it is seen that kernel_checkout and validate_branches are
run again in simultaneous builds. During do_patch the kgit-s2q mechanism
looks for a sentinel file inside the .git directory, finds a fence post
and starts picking up patches after that.

This can create trouble as validate_branches checks out the HEAD of the
branch and so the patches should be reapplied rather than skipped due to
finding of the fence post.

We can call kgit-s2q --clean to remove the sentinel file when the
branches are checked out.

Signed-off-by: Awais Belal 
Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

kernel-yocto: log the BSP definition file

2017-02-05T09:20:21+00:00

When debugging a kernel configuration issue, one of the first questions
is "what BSP was used". To answer this qusetion, we log the BSP .scc
file that was used to generate the kernel configuration in the kernel
source meta directory.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Ross Burton

kern-tools: re-enable scc merge command

2017-02-05T09:20:20+00:00

The ability to merge two branches directly from a .scc file was
dropped during the streamlining of the tools.

As was pointed out by David Vincent , there is
once again a valid use case for this functionality, so we restore the
capability.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Ross Burton

meta/scripts: Various getVar/getVarFlag expansion parameter fixes

2017-01-06T11:46:14+00:00

There were a few straggling expansion parameter removals left for
getVar/getVarFlag where the odd whitespace meant they were missed
on previous passes. There were also some plain broken ussages such
as:

d.getVar('ALTERNATIVE_TARGET', old_name, True)
path = d.getVar('PATH', d, True)
d.getVar('IMAGE_ROOTFS', 'True')

which I've corrected (they happend to work by luck).

Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T08:30:03+00:00

getVar() now defaults to expanding by default, thus remove the True
option from getVar() calls with a regex search and replace.

Search made with the following regex: getVar ?\(( ?[^,()]*), True\)

Signed-off-by: Joshua Lock 
Signed-off-by: Ross Burton

kernel-yocto: explicitly trap subcommand errors

2016-12-13T22:47:32+00:00

To trap errors and halt processing, do_kernel_metadata was recently
switched to exit on any non zero return code. While the concept is
sound, there are subcommands that have legitimate non-zero return
codes.

Instead of removing set +e, we'll explicitly check the return code
of the commands that can error, and throw a bbfatal to alert the
user.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Ross Burton

kernel-yocto: exit on non-zero return code

2016-12-07T10:45:59+00:00

Historically the processing of kernel meta data contained some
commands that exited with a non-zero return code. Special processing
was required to properly deal with their exit.

That is no longer true, and instead of handling all return codes
and doing an explicit 'exit' call, we can remove set -e from the
routine and have all errors be trapped and stop processing.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Ross Burton

utils.bbclass: add function to check for git config user

2016-10-07T15:43:48+00:00

If attempting to patch a git repo without a proper git config setup,
an error will occur saying user.name/user.email are needed by git
am/apply. After some code was removed from kernel-yocto, it was
simple enough to reproduce this error by creating a kernel patch and
using a container to build.

This patch abstracts out functionality that existed in buildhistory
for use in other classes. It also adds a call to this functionality
to the kernel-yocto class.

Fixes [YOCTO #10346]

introduced in OE-core revision
0f698dfd1c8bbc0d53ae7977e26685a7a3df52a3

Signed-off-by: Stephano Cetola 
Signed-off-by: Richard Purdie