Re: [yocto] [yocto-kernel-tools][PATCH] tools/kconf_check: modify grep pattern

[Bruce Ashfield]

On 2018-12-12 8:36 p.m., Hongzhi, Song wrote:

Thanks.

So would you help to remedy the commit log while merging the patch?


I've tweaked the message and added this to my queue. It will
come out early this week.

Bruce




--Hongzhi


On 12/13/2018 02:45 AM, Bruce Ashfield wrote:

On 12/11/18 5:12 AM, Hongzhi.Song wrote:

The cmd line, , can't
match all expect config options.

This is because that it is not always space after 'config'


This should say "not always one space". There really should
always just be a single space, but typos do sneak in. I'll
queue the patch shortly.

Bruce


in kernel-source/*/.../Kconfig.
e.g. "config  IP_VS_IPV6" in net/netfilter/ipvs/Kconfig

So we should change the cmd to grep '^[  ]*\(menu\)*config\s'.

Signed-off-by: Hongzhi.Song 
---
  tools/kconf_check | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/kconf_check b/tools/kconf_check
index aa86180..20b49cd 100755
--- a/tools/kconf_check
+++ b/tools/kconf_check
@@ -241,7 +241,7 @@ find ${kernel_source} \
  # known list of all Kconfig* files.  Again, must filter dups.
  rm -f ${LOGDIR}/all.cfg
  for i in `cat ${LOGDIR}/all.kcf` ; do
-    cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config ' | \
+    cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config\s' | \
  awk '{print "CONFIG_"$2}' >> ${LOGDIR}/all.cfg
  done
  mv -f ${LOGDIR}/all.cfg ${LOGDIR}/all.cfg~








--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH] tools/kconf_check: modify grep pattern

[Hongzhi, Song]

Thanks.

So would you help to remedy the commit log while merging the patch?


--Hongzhi


On 12/13/2018 02:45 AM, Bruce Ashfield wrote:

On 12/11/18 5:12 AM, Hongzhi.Song wrote:

The cmd line, , can't
match all expect config options.

This is because that it is not always space after 'config'


This should say "not always one space". There really should
always just be a single space, but typos do sneak in. I'll
queue the patch shortly.

Bruce


in kernel-source/*/.../Kconfig.
e.g. "config  IP_VS_IPV6" in net/netfilter/ipvs/Kconfig

So we should change the cmd to grep '^[  ]*\(menu\)*config\s'.

Signed-off-by: Hongzhi.Song 
---
  tools/kconf_check | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/kconf_check b/tools/kconf_check
index aa86180..20b49cd 100755
--- a/tools/kconf_check
+++ b/tools/kconf_check
@@ -241,7 +241,7 @@ find ${kernel_source} \
  # known list of all Kconfig* files.  Again, must filter dups.
  rm -f ${LOGDIR}/all.cfg
  for i in `cat ${LOGDIR}/all.kcf` ; do
-    cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config ' | \
+    cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config\s' | \
  awk '{print "CONFIG_"$2}' >> ${LOGDIR}/all.cfg
  done
  mv -f ${LOGDIR}/all.cfg ${LOGDIR}/all.cfg~






--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH] tools/kconf_check: modify grep pattern

[Bruce Ashfield]

On 12/11/18 5:12 AM, Hongzhi.Song wrote:

The cmd line, , can't
match all expect config options.

This is because that it is not always space after 'config'


This should say "not always one space". There really should
always just be a single space, but typos do sneak in. I'll
queue the patch shortly.

Bruce


in kernel-source/*/.../Kconfig.
e.g. "config  IP_VS_IPV6" in net/netfilter/ipvs/Kconfig

So we should change the cmd to grep '^[  ]*\(menu\)*config\s'.

Signed-off-by: Hongzhi.Song 
---
  tools/kconf_check | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/kconf_check b/tools/kconf_check
index aa86180..20b49cd 100755
--- a/tools/kconf_check
+++ b/tools/kconf_check
@@ -241,7 +241,7 @@ find ${kernel_source} \
  # known list of all Kconfig* files.  Again, must filter dups.
  rm -f ${LOGDIR}/all.cfg
  for i in `cat ${LOGDIR}/all.kcf` ; do
-cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config ' | \
+cat ${kernel_source}/$i | grep '^[ ]*\(menu\)*config\s' | \
awk '{print "CONFIG_"$2}' >> ${LOGDIR}/all.cfg
  done
  mv -f ${LOGDIR}/all.cfg ${LOGDIR}/all.cfg~



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

[Bruce Ashfield]

On 2017-02-07 06:21 AM, David Vincent wrote:

On vendredi 3 février 2017 13:51:34 CET Bruce Ashfield wrote:


I was able to merge branches with this patch applied to Morty.

Cheers,

Bruce


I've just successfully tested it on Morty myself. Works for me too, branches
are merged just like they were before !


Good news!

I'll send the patch to the morty maintainer so it can be merged.

Cheers,

Bruce



Thank you
David




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

[David Vincent]

On vendredi 3 février 2017 13:51:34 CET Bruce Ashfield wrote:
> 
> I was able to merge branches with this patch applied to Morty.
> 
> Cheers,
> 
> Bruce
> 
I've just successfully tested it on Morty myself. Works for me too, branches 
are merged just like they were before !

Thank you
David


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

[Bruce Ashfield]

On 2017-02-03 03:42 AM, David Vincent wrote:

On dimanche 29 janvier 2017 23:31:49 CET Bruce Ashfield wrote:

On Wed, Jan 25, 2017 at 1:05 PM, Bruce Ashfield 
wrote:

I spent Friday looking into this in more detail, and to keep things
consistent
with how the path and config queues are handled, with all the tree
manipulations
pull out of the various scripts and exposed in the bbclass itself, I ended
up with
a different implementation of the support.

The kern-tools change is the same as you did (and is your change), the
difference
is in the bbclass processing, where do_patch() modifies the tree, and it
consumes
the output of the meta-data routine .. versus the kgit-meta script itself.

Thanks for looking into this and come up with a better implementation. I agree
that mine was a little harsh.

The work can be seen in my poky-contrib tree:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=zedd/kernel,
in the
commit "kern-tools: re-enable scc merge command".

These changes are on master, and passed my testing to merge feature branches
into the branch being built.

Saw it, read it and saw that it was now in master-next, ready to be pulled.


If you are able to try it out (on master), that would be great. I'm going
to let it
soak for a few days, and once it merges to master, it can be ported to
morty.

Sorry, I don't have a master build ready but as soon as I can test it whether
on morty or master, I will report back.


I was able to merge branches with this patch applied to Morty.

Cheers,

Bruce



David



>From 8e08efa4b567e58386247575ae28835841f484c0 Mon Sep 17 00:00:00 2001
From: Bruce Ashfield 
Date: Wed, 25 Jan 2017 13:29:34 -0500
Subject: [PATCH] kern-tools: re-enable scc merge command

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 
---
 meta/classes/kernel-yocto.bbclass   | 16 +++-
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb |  3 ++-
 2 files changed, 17 insertions(+), 2 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index a60327a..eb35dce 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -148,7 +148,7 @@ do_kernel_metadata() {
 	# run1: pull all the configuration fragments, no matter where they come from
 	elements="`echo -n ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}`"
 	if [ -n "${elements}" ]; then
-		scc --force -o ${S}/${meta_dir}:cfg,meta ${includes} ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}
+		scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}
 		if [ $? -ne 0 ]; then
 			bbfatal_log "Could not generate configuration queue for ${KMACHINE}."
 		fi
@@ -165,6 +165,7 @@ do_kernel_metadata() {
 }
 
 do_patch() {
+	set +e
 	cd ${S}
 
 	check_git_config
@@ -177,6 +178,19 @@ do_patch() {
 			bbfatal_log "Patch failures can be resolved in the linux source directory ${S})"
 		fi
 	fi
+
+	if [ -f "${meta_dir}/merge.queue" ]; then
+		# we need to merge all these branches
+		for b in $(cat ${meta_dir}/merge.queue); do
+			git show-ref --verify --quiet refs/heads/${b}
+			if [ $? -eq 0 ]; then
+bbnote "Merging branch ${b}"
+git merge -q --no-ff -m "Merge branch ${b}" ${b}
+			else
+bbfatal "branch ${b} does not exist, cannot merge"
+			fi
+		done
+	fi
 }
 
 do_kernel_checkout() {
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 8af0155..aa27ec8 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,8 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=a6c2fa8aef1b
 
 DEPENDS = "git-native"
 
-SRCREV = "85564e69555b713c2759d58ec5ade54424d051d8"
+SRCREV = "c14440d4e7ae0160c260ed65c3e123be5dc97ae8"
+
 PR = "r12"
 PV = "0.2+git${SRCPV}"
 
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

[Bruce Ashfield]

On 2017-02-03 03:42 AM, David Vincent wrote:

On dimanche 29 janvier 2017 23:31:49 CET Bruce Ashfield wrote:

On Wed, Jan 25, 2017 at 1:05 PM, Bruce Ashfield 
wrote:

I spent Friday looking into this in more detail, and to keep things
consistent
with how the path and config queues are handled, with all the tree
manipulations
pull out of the various scripts and exposed in the bbclass itself, I ended
up with
a different implementation of the support.

The kern-tools change is the same as you did (and is your change), the
difference
is in the bbclass processing, where do_patch() modifies the tree, and it
consumes
the output of the meta-data routine .. versus the kgit-meta script itself.

Thanks for looking into this and come up with a better implementation. I agree
that mine was a little harsh.

The work can be seen in my poky-contrib tree:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=zedd/kernel,
in the
commit "kern-tools: re-enable scc merge command".

These changes are on master, and passed my testing to merge feature branches
into the branch being built.

Saw it, read it and saw that it was now in master-next, ready to be pulled.


If you are able to try it out (on master), that would be great. I'm going
to let it
soak for a few days, and once it merges to master, it can be ported to
morty.

Sorry, I don't have a master build ready but as soon as I can test it whether
on morty or master, I will report back.


Perfect. Since I just sent my kernel series to master, I can flip my
builder to morty and have a look as well. I'd still like to confirm that
it does work in your scenario, but I can do the lifting to get it ready
for morty with a run of my own.

Cheers,

Bruce



David



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

[David Vincent]

On dimanche 29 janvier 2017 23:31:49 CET Bruce Ashfield wrote:
> On Wed, Jan 25, 2017 at 1:05 PM, Bruce Ashfield 
> wrote:
> 
> I spent Friday looking into this in more detail, and to keep things
> consistent
> with how the path and config queues are handled, with all the tree
> manipulations
> pull out of the various scripts and exposed in the bbclass itself, I ended
> up with
> a different implementation of the support.
> 
> The kern-tools change is the same as you did (and is your change), the
> difference
> is in the bbclass processing, where do_patch() modifies the tree, and it
> consumes
> the output of the meta-data routine .. versus the kgit-meta script itself.
Thanks for looking into this and come up with a better implementation. I agree 
that mine was a little harsh.
> The work can be seen in my poky-contrib tree:
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=zedd/kernel,
> in the
> commit "kern-tools: re-enable scc merge command".
> 
> These changes are on master, and passed my testing to merge feature branches
> into the branch being built.
Saw it, read it and saw that it was now in master-next, ready to be pulled.
> 
> If you are able to try it out (on master), that would be great. I'm going
> to let it
> soak for a few days, and once it merges to master, it can be ported to
> morty.
Sorry, I don't have a master build ready but as soon as I can test it whether 
on morty or master, I will report back.

David
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

[Bruce Ashfield]

On Wed, Jan 25, 2017 at 1:05 PM, Bruce Ashfield 
wrote:

>
>
> On Wed, Jan 25, 2017 at 5:37 AM, David Vincent 
> wrote:
>
>> I've recently noticed that, on Morty, feature branches of a Yocto kernel
>> are not
>> merged anymore. This is due to the fact that the meta-series file does not
>> process the git merge commands anymore.
>>
>
> Indeed. I dropped that functionality on purpose when I did the
> simplification
> and streamlining of the processing .. since I wanted to see if anyone was
> using it.
>
> I now have my answer :D
>
> I need to have a closer look at the patch and run it through some tests
> here, but  on my glance, you've done it correctly.
>
>
>> This commit creates a new merge command to be executed when processing the
>> kernel metadata. To solve the issue, there is also a patch to send to
>> oe-core
>> for kernel-yocto.bbclass, but I wait for this patch to be included since
>> there
>> is no point without it.
>>
>
> Send that patch to me, or I'll just do the patch myself .. since yes, we
> do need
> to add merge to the list of valid comments when processing the meta data.
>
> I'll submit all the changes in my next consolidated pull request for the
> kernels + tools.
>

I spent Friday looking into this in more detail, and to keep things
consistent
with how the path and config queues are handled, with all the tree
manipulations
pull out of the various scripts and exposed in the bbclass itself, I ended
up with
a different implementation of the support.

The kern-tools change is the same as you did (and is your change), the
difference
is in the bbclass processing, where do_patch() modifies the tree, and it
consumes
the output of the meta-data routine .. versus the kgit-meta script itself.

The work can be seen in my poky-contrib tree:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=zedd/kernel,
in the
commit "kern-tools: re-enable scc merge command".

These changes are on master, and passed my testing to merge feature branches
into the branch being built.

If you are able to try it out (on master), that would be great. I'm going
to let it
soak for a few days, and once it merges to master, it can be ported to
morty.

Cheers,

Bruce



>
> Bruce
>
>
>>
>> David Vincent (1):
>>   scc: Move merge command
>>
>>  tools/kgit-meta  | 14 ++
>>  tools/scc| 13 -
>>  tools/scc-cmds/merge.cmd | 10 ++
>>  3 files changed, 24 insertions(+), 13 deletions(-)
>>  create mode 100644 tools/scc-cmds/merge.cmd
>>
>> --
>> 2.11.0
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

[Bruce Ashfield]

On Wed, Jan 25, 2017 at 5:37 AM, David Vincent 
wrote:

> I've recently noticed that, on Morty, feature branches of a Yocto kernel
> are not
> merged anymore. This is due to the fact that the meta-series file does not
> process the git merge commands anymore.
>

Indeed. I dropped that functionality on purpose when I did the
simplification
and streamlining of the processing .. since I wanted to see if anyone was
using it.

I now have my answer :D

I need to have a closer look at the patch and run it through some tests
here, but  on my glance, you've done it correctly.


> This commit creates a new merge command to be executed when processing the
> kernel metadata. To solve the issue, there is also a patch to send to
> oe-core
> for kernel-yocto.bbclass, but I wait for this patch to be included since
> there
> is no point without it.
>

Send that patch to me, or I'll just do the patch myself .. since yes, we do
need
to add merge to the list of valid comments when processing the meta data.

I'll submit all the changes in my next consolidated pull request for the
kernels + tools.

Bruce


>
> David Vincent (1):
>   scc: Move merge command
>
>  tools/kgit-meta  | 14 ++
>  tools/scc| 13 -
>  tools/scc-cmds/merge.cmd | 10 ++
>  3 files changed, 24 insertions(+), 13 deletions(-)
>  create mode 100644 tools/scc-cmds/merge.cmd
>
> --
> 2.11.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools and multiple users

[Philip Balister]

On 12/01/2016 08:34 PM, Bruce Ashfield wrote:
> On 12/01/2016 06:09 PM, Trevor Woerner wrote:
>> On Thu 2016-12-01 @ 05:50:21 PM, Bruce Ashfield wrote:
>>> Can you just provide me the details of exactly how you are invoking
>>> the build that triggers the error ?
>>
>> $ git clone git://git.openembedded.org/openembedded-core.git
>> (HEAD @ 11063a01d4511b2688ea7ba2d7359e4e07328c66)
>> $ git clone git://git.yoctoproject.org/meta-raspberrypi
>> (HEAD @ 44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9)
>> $ git clone git://git.openembedded.org/bitbake.git
>> (HEAD @ 0bb188f01e396052b127e170a25246d79a6d6741)
>>
>> $ openembedded-core/oe-init-build-env raspi2-test bitbake
>> $ bitbake-layers add-layer ../meta-raspberrypi
>>
>> $ MACHINE=raspberrypi2 bitbake virtual/kernel
> 
> FYI: I've found the issue and will bundle it into the /tmp/ fix
> tomorrow.

Awesome, I unstuck myself reverting a commit, but looking forward to a
real fix.

Philip

> 
> Bruce
> 
>>
>> Build Configuration:
>> BB_VERSION= "1.32.0"
>> BUILD_SYS = "x86_64-linux"
>> NATIVELSBSTRING   = "opensuse-42.2"
>> TARGET_SYS= "arm-oe-linux-gnueabi"
>> MACHINE   = "raspberrypi2"
>> DISTRO= "nodistro"
>> DISTRO_VERSION= "nodistro.0"
>> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard
>> cortexa7"
>> TARGET_FPU= "hard"
>> meta  = "master:11063a01d4511b2688ea7ba2d7359e4e07328c66"
>> meta-raspberrypi  = "master:44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9"
>>
>> ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0
>> do_kernel_metadata: Function failed: do_kernel_metadata (log file is
>> located at
>> /z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
>>
>> ERROR: Logfile of failure stored in:
>> /z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670
>>
>> Log data follows:
>> | DEBUG: Executing shell function do_kernel_metadata
>> | [ERROR]: processing of file /tmp/tmp.G7DTQu11V3 failed
>> |
>> /z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
>> line 29: : No such file or directory
>> |
>> | Context around the error is:
>> |
>> | #
>> | prefix
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
>>
>> | kconf non-hardware
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>>
>> | prefix
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
>>
>> | patch
>> "/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
>>
>> | # run time: 0 seconds
>> | # processed files:
>> | # _cfg
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>>
>> | # _cfg
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
>>
>> |
>> | See pre-processed file /tmp/tmp.G7DTQu11V3 for more details
>> | #
>> | # scc v0.8
>> | # processed: Thu Dec  1 18:08:50 EST 2016
>> | #
>> | # This is a scc output file, do not edit
>> | #
>> | [ERROR]: processing of file /tmp/tmp.zvbMU6XqZm failed
>> | # _reloc_dir
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
>> | # _reloc_dir
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
>> |
>> /z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
>> line 29: : No such file or directory
>> |
>> | Context around the error is:
>> |
>> | #
>> | prefix
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
>>
>> | kconf non-hardware
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>>
>> | prefix
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
>>
>> | patch
>> "/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
>>
>> | # run time: 0 seconds
>> | # processed files:
>> | # _cfg
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
>>
>> | # _cfg
>> /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
>>
>> |
>> | See pre-processed file /tmp/tmp.zvbMU6XqZm for more details
>> | ERROR: Function failed: do_kernel_metadata (log file is located at
>> /z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
>>
>> ERROR: Task
>> (/z/layerindex-master/layers/meta-raspberrypi/reci

Re: [yocto] yocto-kernel-tools and multiple users

[Bruce Ashfield]

On 12/01/2016 06:09 PM, Trevor Woerner wrote:

On Thu 2016-12-01 @ 05:50:21 PM, Bruce Ashfield wrote:

Can you just provide me the details of exactly how you are invoking
the build that triggers the error ?


$ git clone git://git.openembedded.org/openembedded-core.git
(HEAD @ 11063a01d4511b2688ea7ba2d7359e4e07328c66)
$ git clone git://git.yoctoproject.org/meta-raspberrypi
(HEAD @ 44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9)
$ git clone git://git.openembedded.org/bitbake.git
(HEAD @ 0bb188f01e396052b127e170a25246d79a6d6741)

$ openembedded-core/oe-init-build-env raspi2-test bitbake
$ bitbake-layers add-layer ../meta-raspberrypi

$ MACHINE=raspberrypi2 bitbake virtual/kernel


FYI: I've found the issue and will bundle it into the /tmp/ fix
tomorrow.

Bruce



Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "opensuse-42.2"
TARGET_SYS= "arm-oe-linux-gnueabi"
MACHINE   = "raspberrypi2"
DISTRO= "nodistro"
DISTRO_VERSION= "nodistro.0"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard
cortexa7"
TARGET_FPU= "hard"
meta  = "master:11063a01d4511b2688ea7ba2d7359e4e07328c66"
meta-raspberrypi  = "master:44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9"

ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0 do_kernel_metadata: 
Function failed: do_kernel_metadata (log file is located at 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
ERROR: Logfile of failure stored in: 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670
Log data follows:
| DEBUG: Executing shell function do_kernel_metadata
| [ERROR]: processing of file /tmp/tmp.G7DTQu11V3 failed
| 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
| kconf non-hardware 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
| patch 
"/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
|
| See pre-processed file /tmp/tmp.G7DTQu11V3 for more details
| #
| # scc v0.8
| # processed: Thu Dec  1 18:08:50 EST 2016
| #
| # This is a scc output file, do not edit
| #
| [ERROR]: processing of file /tmp/tmp.zvbMU6XqZm failed
| # _reloc_dir /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
| # _reloc_dir /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
| 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
| kconf non-hardware 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
| patch 
"/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
|
| See pre-processed file /tmp/tmp.zvbMU6XqZm for more details
| ERROR: Function failed: do_kernel_metadata (log file is located at 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
ERROR: Task 
(/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata)
 failed with exit code '1'



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools and multiple users

[Trevor Woerner]

Awesome! Thanks :-)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools and multiple users

[Bruce Ashfield]

On 12/01/2016 06:09 PM, Trevor Woerner wrote:

On Thu 2016-12-01 @ 05:50:21 PM, Bruce Ashfield wrote:

Can you just provide me the details of exactly how you are invoking
the build that triggers the error ?


$ git clone git://git.openembedded.org/openembedded-core.git
(HEAD @ 11063a01d4511b2688ea7ba2d7359e4e07328c66)
$ git clone git://git.yoctoproject.org/meta-raspberrypi
(HEAD @ 44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9)
$ git clone git://git.openembedded.org/bitbake.git
(HEAD @ 0bb188f01e396052b127e170a25246d79a6d6741)



perfect. Consider it fixed .. with something that shows up
that easily, I'll fix it when I'm doing the mktmp changes.

Bruce


$ openembedded-core/oe-init-build-env raspi2-test bitbake
$ bitbake-layers add-layer ../meta-raspberrypi

$ MACHINE=raspberrypi2 bitbake virtual/kernel

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "opensuse-42.2"
TARGET_SYS= "arm-oe-linux-gnueabi"
MACHINE   = "raspberrypi2"
DISTRO= "nodistro"
DISTRO_VERSION= "nodistro.0"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard
cortexa7"
TARGET_FPU= "hard"
meta  = "master:11063a01d4511b2688ea7ba2d7359e4e07328c66"
meta-raspberrypi  = "master:44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9"

ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0 do_kernel_metadata: 
Function failed: do_kernel_metadata (log file is located at 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
ERROR: Logfile of failure stored in: 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670
Log data follows:
| DEBUG: Executing shell function do_kernel_metadata
| [ERROR]: processing of file /tmp/tmp.G7DTQu11V3 failed
| 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
| kconf non-hardware 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
| patch 
"/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
|
| See pre-processed file /tmp/tmp.G7DTQu11V3 for more details
| #
| # scc v0.8
| # processed: Thu Dec  1 18:08:50 EST 2016
| #
| # This is a scc output file, do not edit
| #
| [ERROR]: processing of file /tmp/tmp.zvbMU6XqZm failed
| # _reloc_dir /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
| # _reloc_dir /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
| 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
| kconf non-hardware 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
| patch 
"/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
|
| See pre-processed file /tmp/tmp.zvbMU6XqZm for more details
| ERROR: Function failed: do_kernel_metadata (log file is located at 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
ERROR: Task 
(/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata)
 failed with exit code '1'



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools and multiple users

[Trevor Woerner]

On Thu 2016-12-01 @ 05:50:21 PM, Bruce Ashfield wrote:
> Can you just provide me the details of exactly how you are invoking
> the build that triggers the error ?

$ git clone git://git.openembedded.org/openembedded-core.git
(HEAD @ 11063a01d4511b2688ea7ba2d7359e4e07328c66)
$ git clone git://git.yoctoproject.org/meta-raspberrypi
(HEAD @ 44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9)
$ git clone git://git.openembedded.org/bitbake.git
(HEAD @ 0bb188f01e396052b127e170a25246d79a6d6741)

$ openembedded-core/oe-init-build-env raspi2-test bitbake
$ bitbake-layers add-layer ../meta-raspberrypi

$ MACHINE=raspberrypi2 bitbake virtual/kernel

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "opensuse-42.2"
TARGET_SYS= "arm-oe-linux-gnueabi"
MACHINE   = "raspberrypi2"
DISTRO= "nodistro"
DISTRO_VERSION= "nodistro.0"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard
cortexa7"
TARGET_FPU= "hard"
meta  = "master:11063a01d4511b2688ea7ba2d7359e4e07328c66"
meta-raspberrypi  = "master:44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9"

ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0 do_kernel_metadata: 
Function failed: do_kernel_metadata (log file is located at 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
ERROR: Logfile of failure stored in: 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670
Log data follows:
| DEBUG: Executing shell function do_kernel_metadata
| [ERROR]: processing of file /tmp/tmp.G7DTQu11V3 failed
| 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory
| 
| Context around the error is:
| 
| #
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
| kconf non-hardware 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
| patch 
"/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
| 
| See pre-processed file /tmp/tmp.G7DTQu11V3 for more details
| #
| # scc v0.8
| # processed: Thu Dec  1 18:08:50 EST 2016
| #
| # This is a scc output file, do not edit
| #
| [ERROR]: processing of file /tmp/tmp.zvbMU6XqZm failed
| # _reloc_dir /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
| # _reloc_dir /z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux
| 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory
| 
| Context around the error is:
| 
| #
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/
| kconf non-hardware 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| prefix 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/
| patch 
"/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
| # _cfg 
/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
| 
| See pre-processed file /tmp/tmp.zvbMU6XqZm for more details
| ERROR: Function failed: do_kernel_metadata (log file is located at 
/z/layerindex-master/raspi2-basic-2/tmp-glibc/work/raspberrypi2-oe-linux-gnueabi/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.9670)
ERROR: Task 
(/z/layerindex-master/layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata)
 failed with exit code '1'

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools and multiple users

[Bruce Ashfield]

On 12/01/2016 05:44 PM, Trevor Woerner wrote:

On Thu 2016-12-01 @ 05:28:20 PM, Bruce Ashfield wrote:

Gah, that's my bad. I'm currently in transit for a trip to Europe, but I'll
fix this
to use mktmp and friends tomorrow and send out a patch.


Great, thanks :-)

I think there might be a second issue too.

When scc-cmds/patch.cmd is run from the native sysroot, it errors out as
follows:

| 
/z/layerindex-master/raspi2-basic/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory

Line 29 of patch.cmd looks like:

eval echo "\"patches/${cbranch_name}/${relative_patch_dir}/${simple_patch_name}\"" 
>> "${branch_patch_queue}"

I *think* it's complaining about "${branch_patch_queue}" but I can't be
certain. Philip is also seeing this (second) issue too. Does that look like
something you can figure out, or should I keep digging?


I can figure it out, it just looks like not all the parts of the
tools are being installed properly.

Can you just provide me the details of exactly how you are invoking
the build that triggers the error ?

Bruce





--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools and multiple users

[Trevor Woerner]

On Thu 2016-12-01 @ 05:28:20 PM, Bruce Ashfield wrote:
> Gah, that's my bad. I'm currently in transit for a trip to Europe, but I'll
> fix this
> to use mktmp and friends tomorrow and send out a patch.

Great, thanks :-)

I think there might be a second issue too.

When scc-cmds/patch.cmd is run from the native sysroot, it errors out as
follows:

| 
/z/layerindex-master/raspi2-basic/tmp-glibc/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
 line 29: : No such file or directory

Line 29 of patch.cmd looks like:

eval echo 
"\"patches/${cbranch_name}/${relative_patch_dir}/${simple_patch_name}\"" >> 
"${branch_patch_queue}"

I *think* it's complaining about "${branch_patch_queue}" but I can't be
certain. Philip is also seeing this (second) issue too. Does that look like
something you can figure out, or should I keep digging?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools and multiple users

[Bruce Ashfield]

On Thu, Dec 1, 2016 at 3:05 PM, Trevor Woerner  wrote:

> I believe a recent change in the yocto-kernel-tools is causing some funny
> issue I saw this morning on my overnight jenkins builds.
>
> commit 08463d684c1952e74c25344cddace4c3f24c739d
> Date:   Mon Oct 31 14:30:12 2016 -0400
>
> scc: exit on error
>
> If there is an error in the processing of the input files, scc
> should exit and inform the user.
>
> scc is executed on a combined/preprocessed file and as a result
> it doesn't have the granularity to see each input file
> individually.
>
> Rather than moving preprocessing into scc (from spp), we can
> trap
> the line number of the error and dump context around the line.
> This
> gives the user a pointer to the input file and the specific
> line
> that caused the problem.
>
> Signed-off-by: Bruce Ashfield 
>
> diff --git a/tools/scc b/tools/scc
> index b6ab747..0294103 100755
> --- a/tools/scc
> +++ b/tools/scc
> @@ -238,18 +238,37 @@ process_file()
>  done
>
>  unset PATH
> -if [ -n "${verbose}" ]; then
> -eval . $in $outfile_append
> -else
> -# hide stderr if we aren't verbose
> -eval . $in $outfile_append 2> /dev/null
> -fi
> +(
> +set -e
> +eval . $in $outfile_append > /tmp/scc-output 2>&1
> +)
> +)
>
> -if [ $? -ne 0 ]; then
> -echo "[ERROR]: processing of file $in failed"
> -exit 1
> +if [ $? -ne 0 ]; then
> +echo "[ERROR]: processing of file $in failed"
> +cat /tmp/scc-output
> +
> +# look for common errors so we can point to the right
> input file
> +
> +# 1) /tmp/tmp.gfN6WsbDHN: line 403: cat: No such file or
> directory
> +# "grep -oh" will only output what matches, which
> gets us "line 404: .."
> +# cut gets us the second field, which is the line
> number
> +line=$(cat /tmp/scc-output | grep -oh "line.*:" | cut -f2
> -d' ' | sed 's/://g')
> +if [ -n "$line" ]; then
> +let start_line=$line-20
> +let end_line=$line+10
> +if [ $start_line -lt 0 ]; then
> +start_line=0
> +fi
> +echo ""
> +echo "Context around the error is:"
> +echo ""
> +sed -n -e "$start_line,$end_line p" -e "$end_line q"
> $in | sed 's/^//'
> +echo ""
> +echo "See pre-processed file $in for more details"
>  fi
> -)
> +exit 1
> +fi
>
>  return 0
>  }
>
> In order to catch errors, scc's output is being hardcoded to
> /tmp/scc-output.
> But on my box there are two users who perform builds: jenkins and myself.
> When
> the second person comes along to do a build it finds inadequate
> permissions on
> /tmp/scc-output.
>
> Is anyone else seeing this?
>



Gah, that's my bad. I'm currently in transit for a trip to Europe, but I'll
fix this
to use mktmp and friends tomorrow and send out a patch.

Bruce


> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools

[Darren Hart]

On 12/24/2012 08:15 AM, Bruce Ashfield wrote:
> 
> 
> 
> On Mon, Dec 24, 2012 at 6:28 AM, Rick Yang  > wrote:
> 
> Hi , 
> 
> We have a linux release base on yocto, and we want to use
> yocto-kernel-tools to manage kernel configuration fragments, instead
> of the old method. So we want to know, when poky will use
> yocto-kernel-tools to manage the kernel ? Is there a plan?
> 
> 
> I'm not sure I follow the question. Since yocto 1.0 the kern-tools have
> been used
> to manage the kernel, they've been changing over time, but the
> foundation and
> theory is the same.
> 
> If you want to manage a custom kernel, have a look in meta-skeleton for 
> linux-yocto-custom.bb  and you can apply
> fragments to any upstream git tree
> of your choosing. It would of course be better if we get more
> contributions to the
> main linux-yocto meta data (yocto-kernel-cache and the linux-yocto meta
> branch), but
> that's completely voluntary. 

If you need some documentation on this please let us know, we have some
early docs going through some active development we can point you at if
interested.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto-kernel-tools

[Bruce Ashfield]

On Mon, Dec 24, 2012 at 6:28 AM, Rick Yang  wrote:

>  Hi , 
>
> We have a linux release base on yocto, and we want to use
> yocto-kernel-tools to manage kernel configuration fragments, instead of the
> old method. So we want to know, when poky will use yocto-kernel-tools to
> manage the kernel ? Is there a plan?
>

I'm not sure I follow the question. Since yocto 1.0 the kern-tools have
been used
to manage the kernel, they've been changing over time, but the foundation
and
theory is the same.

If you want to manage a custom kernel, have a look in meta-skeleton for
linux-yocto-custom.bb and you can apply fragments to any upstream git tree
of your choosing. It would of course be better if we get more contributions
to the
main linux-yocto meta data (yocto-kernel-cache and the linux-yocto meta
branch), but
that's completely voluntary.

Cheers,

Bruce


> 
>
> ** **
>
> Thanks!
>
> ** **
>
> Rick
>
> ** **
>
> ** **
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto