Re: [yocto] SRCREV issue with linux-yocto-custom do_validate_branches()
On 04/21/2015 08:21 AM, Mills, Clayton wrote:
On 17 April 2015 14:28, Bruce Ashfield wrote:
On 2015-04-17 6:12 AM, Mills, Clayton wrote:
Hi All,
I'm having a little trouble with do_validate_branches() inherited by my
linux-yocto-custom.
I'm building the 3.14.28 kernel with ltsi kernel patch set applied, so was
trying to set this up with a custom linux recipe in my bsp.
Out of curiosity, was something missing in the linux-yocto 3.14 LTSI
integration ? I'll comment on the specifics below, but I was wondering about
that high level point as well.
I'll admit I'm new to yocto so if I've missed where I could have easily
selected v3.14.28-ltsi along the way then my bad. Unfortunate because I'm
probably making more work for myself. Though this is probably as good an
opportunity for learning my way around. To be honest in the very near future I
will be building from a branch that is forked off of v3.14.28-ltsi with some
custom stuff anyway, so perhaps this isn't a complete waste of time.
Feel free to expand on what I should be doing. Like I said, I'm new to yocto.
The kernel's that we select for release with the fall Yocto project are
LTSI kernel versions.
As such, the LTSI changes are merged into both a standalone branch, and
then into
each and every BSP branch in the kernel. So any of the SRCREVs that you
get by default
for the qemu* BSPs have the LTSI content integrated and present. For
custom BSPs,
they can branch from standard/base and have that same LTSI content
present in their
build.
Pointing to a branch in my own git repo that has the patch set pre-applied.
I've got a clone of dizzy. Which I used yocto-bsp create to start my bsp layer.
But the process stops in do_validate_branches() with the following error log:
--
--
DEBUG: Executing shell function do_validate_branches
usage: git cat-file (-t|-s|-e|-p||--textconv)
or: git cat-file (--batch|--batch-check) <
can be one of: blob, tree, commit, tag
-tshow object type
-sshow object size
-eexit with zero when there's no error
-ppretty-print object's content
--textconvfor blob objects, run textconv on object's content
--batch[=]show info and content of objects fed from the
standard input
--batch-check[=]
show info about objects fed from the
standard input
ERROR: is not a valid commit ID.
ERROR: The kernel source tree may be out of sync
WARNING: exit code 1 from a shell command.
Do you have the entire log pastebin'd somewhere ? It would be nice to know if
this is the meta, or machine validation that is getting an empty commit.
ERROR: Function failed: do_validate_branches (log file is located at
/opt/git/poky/build/tmp/work/mylayer-poky-linux-gnueabi/linux-yocto-cu
stom/3.14.28+gitAUTOINC+7035c2a67d-r0/temp/log.do_validate_branches.56
991)
--
--
The do_validate_branches() code from kernel-yocto.bbclass is as follows...
--
-- # Ensure that the branches (BSP and meta) are on the
locations specified by # their SRCREV values. If they are NOT on the
right commits, the branches # are corrected to the proper commit.
do_validate_branches() {
set +e
cd ${S}
export KMETA=${KMETA}
machine_branch="${@ get_machine_branch(d, "${KBRANCH}" )}"
machine_srcrev="${SRCREV_machine}"
# if SRCREV is AUTOREV it shows up as AUTOINC there's nothing to
# check and we can exit early
if [ "${machine_srcrev}" = "AUTOINC" ]; then
bbnote "SRCREV validation is not required for AUTOREV"
elif [ "${machine_srcrev}" = "" ] && [ "${SRCREV}" != "AUTOINC" ];
then
# SRCREV_machine_ was not set. This means that a
custom recipe
# that doesn't use the SRCREV_FORMAT "machine_meta" is being
built. In
# this case, we need to reset to the give SRCREV before
heading to patching
bbnote "custom recipe is being built, forcing SRCREV to
${SRCREV}"
force_srcrev="${SRCREV}"
else
git cat-file -t ${machine_srcrev} > /dev/null
if [ $? -ne 0 ]; then
bberror "${machine_srcrev} is not a valid commit ID."
bbfatal "The kernel source tree may be out of sync"
fi
force_srcrev=${machine_srcrev}
fi
## KMETA branch validation.
target_meta_head="${SRCREV_meta}"
if [ "${target_meta_head}" = "AUTOINC" ] || [ "${target_meta_head}" =
"" ]; then
bbnote "SRCREV validation skipped for AUTOREV or empty meta
branch
Re: [yocto] SRCREV issue with linux-yocto-custom do_validate_branches()
> On 17 April 2015 14:28, Bruce Ashfield wrote:
>
> On 2015-04-17 6:12 AM, Mills, Clayton wrote:
> > Hi All,
> >
> > I'm having a little trouble with do_validate_branches() inherited by my
> > linux-yocto-custom.
> > I'm building the 3.14.28 kernel with ltsi kernel patch set applied, so was
> > trying to set this up with a custom linux recipe in my bsp.
>
> Out of curiosity, was something missing in the linux-yocto 3.14 LTSI
> integration ? I'll comment on the specifics below, but I was wondering about
> that high level point as well.
I'll admit I'm new to yocto so if I've missed where I could have easily
selected v3.14.28-ltsi along the way then my bad. Unfortunate because I'm
probably making more work for myself. Though this is probably as good an
opportunity for learning my way around. To be honest in the very near future I
will be building from a branch that is forked off of v3.14.28-ltsi with some
custom stuff anyway, so perhaps this isn't a complete waste of time.
Feel free to expand on what I should be doing. Like I said, I'm new to yocto.
>
> > Pointing to a branch in my own git repo that has the patch set pre-applied.
> > I've got a clone of dizzy. Which I used yocto-bsp create to start my bsp
> > layer.
> >
> > But the process stops in do_validate_branches() with the following error
> > log:
> > --
> > --
> > DEBUG: Executing shell function do_validate_branches
> > usage: git cat-file (-t|-s|-e|-p||--textconv)
> > or: git cat-file (--batch|--batch-check) <
> >
> > can be one of: blob, tree, commit, tag
> > -tshow object type
> > -sshow object size
> > -eexit with zero when there's no error
> > -ppretty-print object's content
> > --textconvfor blob objects, run textconv on object's
> > content
> > --batch[=]show info and content of objects fed from the
> > standard input
> > --batch-check[=]
> >show info about objects fed from the
> > standard input
> >
> > ERROR: is not a valid commit ID.
> > ERROR: The kernel source tree may be out of sync
> > WARNING: exit code 1 from a shell command.
>
> Do you have the entire log pastebin'd somewhere ? It would be nice to know if
> this is the meta, or machine validation that is getting an empty commit.
>
> > ERROR: Function failed: do_validate_branches (log file is located at
> > /opt/git/poky/build/tmp/work/mylayer-poky-linux-gnueabi/linux-yocto-cu
> > stom/3.14.28+gitAUTOINC+7035c2a67d-r0/temp/log.do_validate_branches.56
> > 991)
> > --
> > --
> >
> >
> > The do_validate_branches() code from kernel-yocto.bbclass is as follows...
> > --
> > -- # Ensure that the branches (BSP and meta) are on the
> > locations specified by # their SRCREV values. If they are NOT on the
> > right commits, the branches # are corrected to the proper commit.
> > do_validate_branches() {
> > set +e
> > cd ${S}
> > export KMETA=${KMETA}
> >
> > machine_branch="${@ get_machine_branch(d, "${KBRANCH}" )}"
> >
> > machine_srcrev="${SRCREV_machine}"
> >
> > # if SRCREV is AUTOREV it shows up as AUTOINC there's nothing to
> > # check and we can exit early
> > if [ "${machine_srcrev}" = "AUTOINC" ]; then
> > bbnote "SRCREV validation is not required for AUTOREV"
> > elif [ "${machine_srcrev}" = "" ] && [ "${SRCREV}" != "AUTOINC" ];
> > then
> > # SRCREV_machine_ was not set. This means that a
> > custom recipe
> > # that doesn't use the SRCREV_FORMAT "machine_meta" is
> > being built. In
> > # this case, we need to reset to the give SRCREV before
> > heading to patching
> > bbnote "custom recipe is being built, forcing SRCREV to
> > ${SRCREV}"
> > force_srcrev="${SRCREV}"
> > else
> > git cat-file -t ${machine_srcrev} > /dev/null
> > if [ $? -ne 0 ]; then
> > bberror "${machine_srcrev} is not a valid commit
> > ID."
> > bbfatal "The kernel source tree may be out of sync"
> > fi
> > force_srcrev=${machine_srcrev}
> > fi
> >
> > ## KMETA branch validation.
> > target_meta_head="${SRCREV_meta}"
> > if [ "${target_meta_head}" = "AUTOINC" ] || [
> > "${target_meta_head}" = "" ]; then
> > bbnote "SRCREV validation skipped for AUTOREV or empty
> > meta branch"
> > else
> > meta_head=`git show-ref -s --heads ${KMETA}`
> >
> > git cat-file -t ${target_meta_head} > /dev/null
> >
Re: [yocto] SRCREV issue with linux-yocto-custom do_validate_branches()
On 2015-04-17 6:12 AM, Mills, Clayton wrote:
Hi All,
I'm having a little trouble with do_validate_branches() inherited by my
linux-yocto-custom.
I'm building the 3.14.28 kernel with ltsi kernel patch set applied, so was
trying to set this up with a custom linux recipe in my bsp.
Out of curiosity, was something missing in the linux-yocto 3.14 LTSI
integration ? I'll comment on the specifics below, but I was wondering
about that high level point as well.
Pointing to a branch in my own git repo that has the patch set pre-applied.
I've got a clone of dizzy. Which I used yocto-bsp create to start my bsp layer.
But the process stops in do_validate_branches() with the following error log:
DEBUG: Executing shell function do_validate_branches
usage: git cat-file (-t|-s|-e|-p||--textconv)
or: git cat-file (--batch|--batch-check) <
can be one of: blob, tree, commit, tag
-tshow object type
-sshow object size
-eexit with zero when there's no error
-ppretty-print object's content
--textconvfor blob objects, run textconv on object's content
--batch[=]show info and content of objects fed from the
standard input
--batch-check[=]
show info about objects fed from the standard input
ERROR: is not a valid commit ID.
ERROR: The kernel source tree may be out of sync
WARNING: exit code 1 from a shell command.
Do you have the entire log pastebin'd somewhere ? It would be nice to know
if this is the meta, or machine validation that is getting an empty commit.
ERROR: Function failed: do_validate_branches (log file is located at
/opt/git/poky/build/tmp/work/mylayer-poky-linux-gnueabi/linux-yocto-custom/3.14.28+gitAUTOINC+7035c2a67d-r0/temp/log.do_validate_branches.56991)
The do_validate_branches() code from kernel-yocto.bbclass is as follows...
# Ensure that the branches (BSP and meta) are on the locations specified by
# their SRCREV values. If they are NOT on the right commits, the branches
# are corrected to the proper commit.
do_validate_branches() {
set +e
cd ${S}
export KMETA=${KMETA}
machine_branch="${@ get_machine_branch(d, "${KBRANCH}" )}"
machine_srcrev="${SRCREV_machine}"
# if SRCREV is AUTOREV it shows up as AUTOINC there's nothing to
# check and we can exit early
if [ "${machine_srcrev}" = "AUTOINC" ]; then
bbnote "SRCREV validation is not required for AUTOREV"
elif [ "${machine_srcrev}" = "" ] && [ "${SRCREV}" != "AUTOINC" ]; then
# SRCREV_machine_ was not set. This means that a
custom recipe
# that doesn't use the SRCREV_FORMAT "machine_meta" is being
built. In
# this case, we need to reset to the give SRCREV before
heading to patching
bbnote "custom recipe is being built, forcing SRCREV to
${SRCREV}"
force_srcrev="${SRCREV}"
else
git cat-file -t ${machine_srcrev} > /dev/null
if [ $? -ne 0 ]; then
bberror "${machine_srcrev} is not a valid commit ID."
bbfatal "The kernel source tree may be out of sync"
fi
force_srcrev=${machine_srcrev}
fi
## KMETA branch validation.
target_meta_head="${SRCREV_meta}"
if [ "${target_meta_head}" = "AUTOINC" ] || [ "${target_meta_head}" =
"" ]; then
bbnote "SRCREV validation skipped for AUTOREV or empty meta
branch"
else
meta_head=`git show-ref -s --heads ${KMETA}`
git cat-file -t ${target_meta_head} > /dev/null
if [ $? -ne 0 ]; then
bberror "${target_meta_head} is not a valid commit ID"
bbfatal "The kernel source tree may be out of sync"
fi
if [ "$meta_head" != "$target_meta_head" ]; then
bbnote "Setting branch ${KMETA} to ${target_meta_head}"
git branch -m ${KMETA} ${KMETA}-orig
git checkout -q -b ${KMETA} ${target_meta_head}
if [ $? -ne 0 ];then
bbfatal "Could not checkout ${KMETA} branch from
known hash ${target_meta_head}"
fi
fi
fi
git checkout -q -f ${machine_branch}
if [ -n "${force_srcrev}" ]; then
# see if the branch we are about to patch has been properly
reset to the defined
# SRCREV .. if not, we reset it.
[yocto] SRCREV issue with linux-yocto-custom do_validate_branches()
Hi All,
I'm having a little trouble with do_validate_branches() inherited by my
linux-yocto-custom.
I'm building the 3.14.28 kernel with ltsi kernel patch set applied, so was
trying to set this up with a custom linux recipe in my bsp.
Pointing to a branch in my own git repo that has the patch set pre-applied.
I've got a clone of dizzy. Which I used yocto-bsp create to start my bsp layer.
But the process stops in do_validate_branches() with the following error log:
DEBUG: Executing shell function do_validate_branches
usage: git cat-file (-t|-s|-e|-p||--textconv)
or: git cat-file (--batch|--batch-check) <
can be one of: blob, tree, commit, tag
-tshow object type
-sshow object size
-eexit with zero when there's no error
-ppretty-print object's content
--textconvfor blob objects, run textconv on object's content
--batch[=]show info and content of objects fed from the
standard input
--batch-check[=]
show info about objects fed from the standard input
ERROR: is not a valid commit ID.
ERROR: The kernel source tree may be out of sync
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_validate_branches (log file is located at
/opt/git/poky/build/tmp/work/mylayer-poky-linux-gnueabi/linux-yocto-custom/3.14.28+gitAUTOINC+7035c2a67d-r0/temp/log.do_validate_branches.56991)
The do_validate_branches() code from kernel-yocto.bbclass is as follows...
# Ensure that the branches (BSP and meta) are on the locations specified by
# their SRCREV values. If they are NOT on the right commits, the branches
# are corrected to the proper commit.
do_validate_branches() {
set +e
cd ${S}
export KMETA=${KMETA}
machine_branch="${@ get_machine_branch(d, "${KBRANCH}" )}"
machine_srcrev="${SRCREV_machine}"
# if SRCREV is AUTOREV it shows up as AUTOINC there's nothing to
# check and we can exit early
if [ "${machine_srcrev}" = "AUTOINC" ]; then
bbnote "SRCREV validation is not required for AUTOREV"
elif [ "${machine_srcrev}" = "" ] && [ "${SRCREV}" != "AUTOINC" ]; then
# SRCREV_machine_ was not set. This means that a
custom recipe
# that doesn't use the SRCREV_FORMAT "machine_meta" is being
built. In
# this case, we need to reset to the give SRCREV before heading
to patching
bbnote "custom recipe is being built, forcing SRCREV to
${SRCREV}"
force_srcrev="${SRCREV}"
else
git cat-file -t ${machine_srcrev} > /dev/null
if [ $? -ne 0 ]; then
bberror "${machine_srcrev} is not a valid commit ID."
bbfatal "The kernel source tree may be out of sync"
fi
force_srcrev=${machine_srcrev}
fi
## KMETA branch validation.
target_meta_head="${SRCREV_meta}"
if [ "${target_meta_head}" = "AUTOINC" ] || [ "${target_meta_head}" =
"" ]; then
bbnote "SRCREV validation skipped for AUTOREV or empty meta
branch"
else
meta_head=`git show-ref -s --heads ${KMETA}`
git cat-file -t ${target_meta_head} > /dev/null
if [ $? -ne 0 ]; then
bberror "${target_meta_head} is not a valid commit ID"
bbfatal "The kernel source tree may be out of sync"
fi
if [ "$meta_head" != "$target_meta_head" ]; then
bbnote "Setting branch ${KMETA} to ${target_meta_head}"
git branch -m ${KMETA} ${KMETA}-orig
git checkout -q -b ${KMETA} ${target_meta_head}
if [ $? -ne 0 ];then
bbfatal "Could not checkout ${KMETA} branch
from known hash ${target_meta_head}"
fi
fi
fi
git checkout -q -f ${machine_branch}
if [ -n "${force_srcrev}" ]; then
# see if the branch we are about to patch has been properly
reset to the defined
# SRCREV .. if not, we reset it.
branch_head=`git rev-parse HEAD`
if [ "${force_srcrev}" != "${branch_head}" ]; then
current_branch=`git rev-parse --abbrev-ref HEAD`
git branch "$current_branch-orig"
git reset --hard ${force_srcrev}
fi
fi
}
It seems like the problem is..
Re: [yocto] SRCREV Issue for custom linux kernel
Hi Bruce,
Thank you for your reply.
I modified the do_validate_sources function in kernel_yocto.bbclasses and now
it is working.
This issue is resolved now.
I have another issue with the package building. While I am trying to build a
package which is not present in open embedded git source i got the oe_runmake
errors.
I wrote a recipe for that package by following the commands given by the yocto
project manual.
Could help me in resolving this.
Thanks in advance.
Regards,
Raghavendra K.
From: Bruce Ashfield
Sent: Friday, April 17, 2015 10:04 AM
To: Raghavendra Kakarla; yocto@yoctoproject.org
Subject: Re: [yocto] SRCREV Issue for custom linux kernel
On 2015-04-15 1:38 AM, Raghavendra Kakarla wrote:
> Hi Bruce,
>
> My recipe is like following:
>
>
> # oe-core kernel classes to apply a subset of yocto kernel
> # management to git managed kernel repositories.
> #
> # Warning:
> #
> # Building this kernel without providing a defconfig or BSP
> # configuration will result in build or boot errors. This is not a
> # bug.
> #
> # Notes:
> #
> # patches: patches can be merged into to the source git tree itself,
> #added via the SRC_URI, or controlled via a BSP
> #configuration.
> #
> # example configuration addition:
> #SRC_URI += "file://smp.cfg"
> # example patch addition:
> #SRC_URI += "file://0001-linux-version-tweak.patch
> # example feature addition:
> #SRC_URI += "file://feature.scc"
> #
>
> inherit kernel
> require recipes-kernel/linux/linux-yocto.inc
>
> SRC_URI =
> "svn://192.168.24.190:9090/svn/trunk/code/kernels;module=linux-3.10.14;protocol=http;user=admin;pswd=Welcome123"
I don't have a SVN server with the linux kernel handy, so I wasn't able
to test this exact same configuration. But I can say a similar git
configuration to kernel.org, or to a tgz worked when I tried a test
build.
Looking through the code more .. this is simply a case that isn't common
or anticipated. The mixing of the SVN SRCREV and the linux-yocto-custom
means that the code that follows is looking to manipulate the tree as a
git repository.
Can you look at your linux source directory in the build, and see if
the SVN checkout has been converted to a git repo ?
If so, the workaround would be to set SRCREV_machine = "AUTOREV", and
that should short circuit the SRCREV validation that simply won't be
correct for a converted git tree.
Alternatively, you can also create an override to do_validate_branches
and stub out the functionality completely.
Bruce
> SRC_URI += "file://defconfig"
>
> SRC_URI += "file://arqlyn.scc \
> file://arqlyn.cfg \
> file://arqlyn-user-config.cfg \
> file://arqlyn-user-patches.scc \
> "
>
>
> LINUX_VERSION ?= "3.10.14"
> LINUX_VERSION_EXTENSION ?= "-custom"
> SRCREV = "94"
> PR = "r0"
> PV = "${LINUX_VERSION}"
> S = "${WORKDIR}/linux-3.10.14"
> COMPATIBLE_MACHINE_arqlyn = "arqlyn"
>
>
> Regards,
>
> Raghavendra
>
>
> From: Bruce Ashfield
> Sent: Tuesday, April 14, 2015 5:36 PM
> To: Raghavendra Kakarla; yocto@yoctoproject.org
> Subject: Re: [yocto] SRCREV Issue for custom linux kernel
>
> On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote:
>> Hi All,
>>
>> I got the an error while i am checking out the linux kernel from the SVN to
>> build in the YOCTO project environment.
>>
>
> What release is this ? master ? An older release ?
>
> And are you seeing this same error if you have a kernel recipe
> that builds from git ? i.e. one of the Yocto reference boards
> with a similar SRCREV ?
>
> The yocto kernel's expect to be able to validate the commits
> and then modify the tree with additional git commands, so the
> tree is either in git format, or is converted to a git format
> (in the case of a tgz) .. so it could be that the SVN checkout
> is preventing that conversion from happening.
>
> Bruce
>
>> Could please help me in resolving the Issue.
>>
>>
>> Error log is:
>> Log data follows:
>> | DEBUG: Executing shell function do_validate_branches
>> | NOTE: custom recipe is being built, forcing SRCREV to INVALID
>> | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch
>> | fatal: ambiguous argument 'INVALID': unknown revision or path not in the
>> working tree.
>> | Use '--' to separate paths from revisions
>> | WARNING: exit code 128 from a shell command.
>> | E
Re: [yocto] SRCREV Issue for custom linux kernel
On 2015-04-15 1:38 AM, Raghavendra Kakarla wrote:
Hi Bruce,
My recipe is like following:
# oe-core kernel classes to apply a subset of yocto kernel
# management to git managed kernel repositories.
#
# Warning:
#
# Building this kernel without providing a defconfig or BSP
# configuration will result in build or boot errors. This is not a
# bug.
#
# Notes:
#
# patches: patches can be merged into to the source git tree itself,
#added via the SRC_URI, or controlled via a BSP
#configuration.
#
# example configuration addition:
#SRC_URI += "file://smp.cfg"
# example patch addition:
#SRC_URI += "file://0001-linux-version-tweak.patch
# example feature addition:
#SRC_URI += "file://feature.scc"
#
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
SRC_URI =
"svn://192.168.24.190:9090/svn/trunk/code/kernels;module=linux-3.10.14;protocol=http;user=admin;pswd=Welcome123"
I don't have a SVN server with the linux kernel handy, so I wasn't able
to test this exact same configuration. But I can say a similar git
configuration to kernel.org, or to a tgz worked when I tried a test
build.
Looking through the code more .. this is simply a case that isn't common
or anticipated. The mixing of the SVN SRCREV and the linux-yocto-custom
means that the code that follows is looking to manipulate the tree as a
git repository.
Can you look at your linux source directory in the build, and see if
the SVN checkout has been converted to a git repo ?
If so, the workaround would be to set SRCREV_machine = "AUTOREV", and
that should short circuit the SRCREV validation that simply won't be
correct for a converted git tree.
Alternatively, you can also create an override to do_validate_branches
and stub out the functionality completely.
Bruce
SRC_URI += "file://defconfig"
SRC_URI += "file://arqlyn.scc \
file://arqlyn.cfg \
file://arqlyn-user-config.cfg \
file://arqlyn-user-patches.scc \
"
LINUX_VERSION ?= "3.10.14"
LINUX_VERSION_EXTENSION ?= "-custom"
SRCREV = "94"
PR = "r0"
PV = "${LINUX_VERSION}"
S = "${WORKDIR}/linux-3.10.14"
COMPATIBLE_MACHINE_arqlyn = "arqlyn"
Regards,
Raghavendra
________
From: Bruce Ashfield
Sent: Tuesday, April 14, 2015 5:36 PM
To: Raghavendra Kakarla; yocto@yoctoproject.org
Subject: Re: [yocto] SRCREV Issue for custom linux kernel
On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote:
Hi All,
I got the an error while i am checking out the linux kernel from the SVN to
build in the YOCTO project environment.
What release is this ? master ? An older release ?
And are you seeing this same error if you have a kernel recipe
that builds from git ? i.e. one of the Yocto reference boards
with a similar SRCREV ?
The yocto kernel's expect to be able to validate the commits
and then modify the tree with additional git commands, so the
tree is either in git format, or is converted to a git format
(in the case of a tgz) .. so it could be that the SVN checkout
is preventing that conversion from happening.
Bruce
Could please help me in resolving the Issue.
Error log is:
Log data follows:
| DEBUG: Executing shell function do_validate_branches
| NOTE: custom recipe is being built, forcing SRCREV to INVALID
| NOTE: SRCREV validation skipped for AUTOREV or empty meta branch
| fatal: ambiguous argument 'INVALID': unknown revision or path not in the
working tree.
| Use '--' to separate paths from revisions
| WARNING: exit code 128 from a shell command.
| ERROR: Function failed: do_validate_branches (log file is located at
/home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852)
Thanks in advance.
Regards,
Raghavendra K.
From: yocto-boun...@yoctoproject.org on behalf of
yocto-requ...@yoctoproject.org
Sent: Tuesday, April 14, 2015 2:50 PM
To: yocto@yoctoproject.org
Subject: yocto Digest, Vol 55, Issue 46
Send yocto mailing list submissions to
yocto@yoctoproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.yoctoproject.org/listinfo/yocto
or, via email, send a message with subject or body 'help' to
yocto-requ...@yoctoproject.org
You can reach the person managing the list at
yocto-ow...@yoctoproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of yocto digest..."
Today's Topics:
1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla)
--
Message: 1
Date: Tue, 14 Apr 2015 09:20:38 +
From: Raghavendra Kakarla
To: "yocto@yoctop
[yocto] SRCREV Issue
Hi All,
I downloaded the yocto from the following link:
git clone -b dizzy git://git.yoctoproject.org/poky.git
And added the my custom recipe for downloading our custom kernel from SVN.
My recipe is like following:
# oe-core kernel classes to apply a subset of yocto kernel
# management to git managed kernel repositories.
#
# Warning:
#
# Building this kernel without providing a defconfig or BSP
# configuration will result in build or boot errors. This is not a
# bug.
#
# Notes:
#
# patches: patches can be merged into to the source git tree itself,
#added via the SRC_URI, or controlled via a BSP
#configuration.
#
# example configuration addition:
#SRC_URI += "file://smp.cfg"
# example patch addition:
#SRC_URI += "file://0001-linux-version-tweak.patch
# example feature addition:
#SRC_URI += "file://feature.scc"
#
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
SRC_URI =
"svn://192.168.24.190:9090/svn/trunk/code/kernels;module=linux-3.10.14;protocol=http;user=admin;pswd=Welcome123"
SRC_URI += "file://defconfig"
SRC_URI += "file://arqlyn.scc \
file://arqlyn.cfg \
file://arqlyn-user-config.cfg \
file://arqlyn-user-patches.scc \
"
LINUX_VERSION ?= "3.10.14"
LINUX_VERSION_EXTENSION ?= "-custom"
SRCREV = "94"
PR = "r0"
PV = "${LINUX_VERSION}"
S = "${WORKDIR}/linux-3.10.14"
COMPATIBLE_MACHINE_arqlyn = "arqlyn"
When I take kernel from the SVN I got the validation error that SRCREV is not
proper.
Could you please help me in resolving this issue.
Regards,
Raghavendra.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SRCREV Issue for custom linux kernel
Hi Bruce,
My recipe is like following:
# oe-core kernel classes to apply a subset of yocto kernel
# management to git managed kernel repositories.
#
# Warning:
#
# Building this kernel without providing a defconfig or BSP
# configuration will result in build or boot errors. This is not a
# bug.
#
# Notes:
#
# patches: patches can be merged into to the source git tree itself,
#added via the SRC_URI, or controlled via a BSP
#configuration.
#
# example configuration addition:
#SRC_URI += "file://smp.cfg"
# example patch addition:
#SRC_URI += "file://0001-linux-version-tweak.patch
# example feature addition:
#SRC_URI += "file://feature.scc"
#
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
SRC_URI =
"svn://192.168.24.190:9090/svn/trunk/code/kernels;module=linux-3.10.14;protocol=http;user=admin;pswd=Welcome123"
SRC_URI += "file://defconfig"
SRC_URI += "file://arqlyn.scc \
file://arqlyn.cfg \
file://arqlyn-user-config.cfg \
file://arqlyn-user-patches.scc \
"
LINUX_VERSION ?= "3.10.14"
LINUX_VERSION_EXTENSION ?= "-custom"
SRCREV = "94"
PR = "r0"
PV = "${LINUX_VERSION}"
S = "${WORKDIR}/linux-3.10.14"
COMPATIBLE_MACHINE_arqlyn = "arqlyn"
Regards,
Raghavendra
____
From: Bruce Ashfield
Sent: Tuesday, April 14, 2015 5:36 PM
To: Raghavendra Kakarla; yocto@yoctoproject.org
Subject: Re: [yocto] SRCREV Issue for custom linux kernel
On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote:
> Hi All,
>
> I got the an error while i am checking out the linux kernel from the SVN to
> build in the YOCTO project environment.
>
What release is this ? master ? An older release ?
And are you seeing this same error if you have a kernel recipe
that builds from git ? i.e. one of the Yocto reference boards
with a similar SRCREV ?
The yocto kernel's expect to be able to validate the commits
and then modify the tree with additional git commands, so the
tree is either in git format, or is converted to a git format
(in the case of a tgz) .. so it could be that the SVN checkout
is preventing that conversion from happening.
Bruce
> Could please help me in resolving the Issue.
>
>
> Error log is:
> Log data follows:
> | DEBUG: Executing shell function do_validate_branches
> | NOTE: custom recipe is being built, forcing SRCREV to INVALID
> | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch
> | fatal: ambiguous argument 'INVALID': unknown revision or path not in the
> working tree.
> | Use '--' to separate paths from revisions
> | WARNING: exit code 128 from a shell command.
> | ERROR: Function failed: do_validate_branches (log file is located at
> /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852)
>
>
> Thanks in advance.
>
> Regards,
>
> Raghavendra K.
>
> From: yocto-boun...@yoctoproject.org on
> behalf of yocto-requ...@yoctoproject.org
> Sent: Tuesday, April 14, 2015 2:50 PM
> To: yocto@yoctoproject.org
> Subject: yocto Digest, Vol 55, Issue 46
>
> Send yocto mailing list submissions to
> yocto@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-requ...@yoctoproject.org
>
> You can reach the person managing the list at
> yocto-ow...@yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
> 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla)
>
>
> --
>
> Message: 1
> Date: Tue, 14 Apr 2015 09:20:38 +
> From: Raghavendra Kakarla
> To: "yocto@yoctoproject.org"
> Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97
> Message-ID: <1429003199394.19...@inedasystems.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi All,
>
> When I take kernel from the SVN I got the validation error that SRCREV is not
> proper.
>
> Could you please help me in resolving this issue.
>
> Thanks in advance.
>
> Regards,
> Raghavendra.
>
>
>
> From: yocto-boun...@yoctoproject.org on
> behalf of yocto-requ...@yoctoproject.org
> Sent: Saturday, February 21, 2015 4:04 AM
> To: yocto@yoctoproject.org
> Subject:
Re: [yocto] SRCREV Issue for custom linux kernel
Hi Bruce, I downloaded the yocto from the following link: git clone -b dizzy git://git.yoctoproject.org/poky.git And added the my custom recipe for downloading our custom kernel from SVN. This gives the error. Regards, Raghavendra. From: Bruce Ashfield Sent: Tuesday, April 14, 2015 5:36 PM To: Raghavendra Kakarla; yocto@yoctoproject.org Subject: Re: [yocto] SRCREV Issue for custom linux kernel On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote: > Hi All, > > I got the an error while i am checking out the linux kernel from the SVN to > build in the YOCTO project environment. > What release is this ? master ? An older release ? And are you seeing this same error if you have a kernel recipe that builds from git ? i.e. one of the Yocto reference boards with a similar SRCREV ? The yocto kernel's expect to be able to validate the commits and then modify the tree with additional git commands, so the tree is either in git format, or is converted to a git format (in the case of a tgz) .. so it could be that the SVN checkout is preventing that conversion from happening. Bruce > Could please help me in resolving the Issue. > > > Error log is: > Log data follows: > | DEBUG: Executing shell function do_validate_branches > | NOTE: custom recipe is being built, forcing SRCREV to INVALID > | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch > | fatal: ambiguous argument 'INVALID': unknown revision or path not in the > working tree. > | Use '--' to separate paths from revisions > | WARNING: exit code 128 from a shell command. > | ERROR: Function failed: do_validate_branches (log file is located at > /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852) > > > Thanks in advance. > > Regards, > > Raghavendra K. > > From: yocto-boun...@yoctoproject.org on > behalf of yocto-requ...@yoctoproject.org > Sent: Tuesday, April 14, 2015 2:50 PM > To: yocto@yoctoproject.org > Subject: yocto Digest, Vol 55, Issue 46 > > Send yocto mailing list submissions to > yocto@yoctoproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.yoctoproject.org/listinfo/yocto > or, via email, send a message with subject or body 'help' to > yocto-requ...@yoctoproject.org > > You can reach the person managing the list at > yocto-ow...@yoctoproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of yocto digest..." > > > Today's Topics: > > 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla) > > > -- > > Message: 1 > Date: Tue, 14 Apr 2015 09:20:38 + > From: Raghavendra Kakarla > To: "yocto@yoctoproject.org" > Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97 > Message-ID: <1429003199394.19...@inedasystems.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi All, > > When I take kernel from the SVN I got the validation error that SRCREV is not > proper. > > Could you please help me in resolving this issue. > > Thanks in advance. > > Regards, > Raghavendra. > > > > From: yocto-boun...@yoctoproject.org on > behalf of yocto-requ...@yoctoproject.org > Sent: Saturday, February 21, 2015 4:04 AM > To: yocto@yoctoproject.org > Subject: yocto Digest, Vol 53, Issue 97 > > Send yocto mailing list submissions to > yocto@yoctoproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.yoctoproject.org/listinfo/yocto > or, via email, send a message with subject or body 'help' to > yocto-requ...@yoctoproject.org > > You can reach the person managing the list at > yocto-ow...@yoctoproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of yocto digest..." > > > Today's Topics: > > 1. Re: Simple recipe quit working in dizzy (akuster) > > > -- > > Message: 1 > Date: Fri, 20 Feb 2015 14:28:10 -0800 > From: akuster > To: yocto@yoctoproject.org > Subject: Re: [yocto] Simple recipe quit working in dizzy > Message-ID: <54e7b4fa@mvista.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > > On 02/20/2015 09:49 AM, Jim Rafert wrote: >> Hi Paul, >> >> Thank you for taki
Re: [yocto] SRCREV Issue for custom linux kernel
On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote: Hi All, I got the an error while i am checking out the linux kernel from the SVN to build in the YOCTO project environment. What release is this ? master ? An older release ? And are you seeing this same error if you have a kernel recipe that builds from git ? i.e. one of the Yocto reference boards with a similar SRCREV ? The yocto kernel's expect to be able to validate the commits and then modify the tree with additional git commands, so the tree is either in git format, or is converted to a git format (in the case of a tgz) .. so it could be that the SVN checkout is preventing that conversion from happening. Bruce Could please help me in resolving the Issue. Error log is: Log data follows: | DEBUG: Executing shell function do_validate_branches | NOTE: custom recipe is being built, forcing SRCREV to INVALID | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch | fatal: ambiguous argument 'INVALID': unknown revision or path not in the working tree. | Use '--' to separate paths from revisions | WARNING: exit code 128 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852) Thanks in advance. Regards, Raghavendra K. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Tuesday, April 14, 2015 2:50 PM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 55, Issue 46 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla) -- Message: 1 Date: Tue, 14 Apr 2015 09:20:38 + From: Raghavendra Kakarla To: "yocto@yoctoproject.org" Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97 Message-ID: <1429003199394.19...@inedasystems.com> Content-Type: text/plain; charset="iso-8859-1" Hi All, When I take kernel from the SVN I got the validation error that SRCREV is not proper. Could you please help me in resolving this issue. Thanks in advance. Regards, Raghavendra. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Saturday, February 21, 2015 4:04 AM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 53, Issue 97 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: Simple recipe quit working in dizzy (akuster) -- Message: 1 Date: Fri, 20 Feb 2015 14:28:10 -0800 From: akuster To: yocto@yoctoproject.org Subject: Re: [yocto] Simple recipe quit working in dizzy Message-ID: <54e7b4fa@mvista.com> Content-Type: text/plain; charset=windows-1252; format=flowed On 02/20/2015 09:49 AM, Jim Rafert wrote: Hi Paul, Thank you for taking an interest in this. I looked at the log.do_rootfs, and didn't see anything that was immediately suspicious. I have inlined the log at the end of my reply, here. I don't see how such a simple recipe could be broken by a Yocto bug, and not have the whole thing be massively broken. Is it possible for you to try your recipe on 'master'? that might tell use if something is missing in dizzy. - Armin -Jim- cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs DEBUG: Executing python function rootfs_process_ignore DEBUG: Python function rootfs_process_ignore finished DEBUG: Executing python function rootfs_runtime_mapping DEBUG: Python function rootfs_runtime_mapping finished DEBUG: Executing python function do_rootfs NOTE: configuring RPM platform settings NOTE: configuring RPM system provides NOTE: configuring RPM DB settings NOTE: configuring Smart settings NOTE: Note: adding Smart channel spectra_ls (35) NOTE: Note: adding Smart channel i586 (30) NOTE: Note: adding Smart channel all (25) NOTE: adding Smart RPM DB channel NOTE: Note: configuring RPM cross-install scriptlet_wrapper NOTE: ## Gene
[yocto] SRCREV Issue for custom linux kernel
Hi All, I got the an error while i am checking out the linux kernel from the SVN to build in the YOCTO project environment. Could please help me in resolving the Issue. Error log is: Log data follows: | DEBUG: Executing shell function do_validate_branches | NOTE: custom recipe is being built, forcing SRCREV to INVALID | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch | fatal: ambiguous argument 'INVALID': unknown revision or path not in the working tree. | Use '--' to separate paths from revisions | WARNING: exit code 128 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852) Thanks in advance. Regards, Raghavendra K. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Tuesday, April 14, 2015 2:50 PM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 55, Issue 46 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla) -- Message: 1 Date: Tue, 14 Apr 2015 09:20:38 + From: Raghavendra Kakarla To: "yocto@yoctoproject.org" Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97 Message-ID: <1429003199394.19...@inedasystems.com> Content-Type: text/plain; charset="iso-8859-1" Hi All, When I take kernel from the SVN I got the validation error that SRCREV is not proper. Could you please help me in resolving this issue. Thanks in advance. Regards, Raghavendra. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Saturday, February 21, 2015 4:04 AM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 53, Issue 97 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: Simple recipe quit working in dizzy (akuster) -- Message: 1 Date: Fri, 20 Feb 2015 14:28:10 -0800 From: akuster To: yocto@yoctoproject.org Subject: Re: [yocto] Simple recipe quit working in dizzy Message-ID: <54e7b4fa@mvista.com> Content-Type: text/plain; charset=windows-1252; format=flowed On 02/20/2015 09:49 AM, Jim Rafert wrote: > Hi Paul, > > Thank you for taking an interest in this. > > I looked at the log.do_rootfs, and didn't see anything that was immediately > suspicious. > I have inlined the log at the end of my reply, here. > > I don't see how such a simple recipe could be broken by a Yocto bug, and not > have the > whole thing be massively broken. Is it possible for you to try your recipe on 'master'? that might tell use if something is missing in dizzy. - Armin > > -Jim- > > cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs > DEBUG: Executing python function rootfs_process_ignore > DEBUG: Python function rootfs_process_ignore finished > DEBUG: Executing python function rootfs_runtime_mapping > DEBUG: Python function rootfs_runtime_mapping finished > DEBUG: Executing python function do_rootfs > NOTE: configuring RPM platform settings > NOTE: configuring RPM system provides > NOTE: configuring RPM DB settings > NOTE: configuring Smart settings > NOTE: Note: adding Smart channel spectra_ls (35) > NOTE: Note: adding Smart channel i586 (30) > NOTE: Note: adding Smart channel all (25) > NOTE: adding Smart RPM DB channel > NOTE: Note: configuring RPM cross-install scriptlet_wrapper > NOTE: ## Generate rootfs ### > NOTE: Executing > '/home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo > --update -q /home/jimr/tera/yocto/dizzy/build/tmp/deploy/rpm/i586' ... > NOTE: Installing the following packages: libgcc1 parted grub dosfstools > psplash vim udev-extraconf rsyslog libsoci nss rpm unzip zip > spectra-postbuild smartpm e2fsprogs-tune2fs packagegroup-core-eclipse-debug > poco libstdc++6 sqlite3 e2fsprogs-e2fsck openssl-staticdev boost > packagegroup-core-ssh-openssh pac
