From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 1/3] yocto-kernel: factor common routes, update to 2.6.37 and branch renaming
Date: Thu, 09 Dec 2010 12:49:08 -0800 [thread overview]
Message-ID: <4D0140C4.5030603@linux.intel.com> (raw)
In-Reply-To: <64f083b7e51bae434b4ae449edc81795e89f9f1c.1291786378.git.bruce.ashfield@windriver.com>
On 12/08/2010 06:35 AM, Bruce Ashfield wrote:
> In order to extend and create more kernel recipes based on the
> supported yocto kernel common routines need to be placed in
> re-usable blocks.
>
> To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
> is broken into three parts:
> .../recipes-kernel/linux/linux-yocto-stable_git.bb | 41 ++++
Now that the git tree permissions for 2.6.37 are public (not sure how
that impacted this) I am still seeing SRC_REV related parsing errors of
linux-yocto-stable_git.bb. Do you have this working Bruce?
$ bitbake linux-yocto-stable
NOTE: Out of date cache found, rebuilding...
NOTE: Handling BitBake files: - (0003/0760) [ 0 %]NOTE: <class
'bb.fetch.InvalidSRCREV'>:Please set SRCREV to a valid value while
evaluating:
${@bb.fetch.get_srcrev(d)}
NOTE: <class 'bb.fetch.InvalidSRCREV'>:Please set SRCREV to a valid
value while evaluating:
${LINUX_VERSION}+git${SRCPV}
NOTE: <class 'bb.fetch.InvalidSRCREV'>:Please set SRCREV to a valid
value while evaluating:
${PN}-${EXTENDPE}${PV}-${PR}
NOTE: <class 'bb.fetch.InvalidSRCREV'>:Please set SRCREV to a valid
value while evaluating:
${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PF}
NOTE: <class 'bb.fetch.InvalidSRCREV'>:Please set SRCREV to a valid
value while evaluating:
${WORKDIR}/linux
NOTE: <class 'bb.fetch.InvalidSRCREV'>:Please set SRCREV to a valid
value while evaluating:
cd ${S}
if [ -f ${WORKDIR}/defconfig ]; then
defconfig=${WORKDIR}/defconfig
fi
if [ -n "${BOOTSTRAP}" ]; then
kbranch="yocto/${LINUX_KERNEL_TYPE}/${KMACHINE}"
else
kbranch=${KBRANCH}
fi
# simply ensures that a branch of the right name has been created
createme ${ARCH} ${kbranch} ${defconfig}
if [ $? -ne 0 ]; then
echo "ERROR. Could not create ${kbranch}"
exit 1
fi
# updates or generates the target description
if [ -n "${KERNEL_FEATURES}" ]; then
addon_features="--features ${KERNEL_FEATURES}"
fi
updateme ${addon_features} ${ARCH} ${WORKDIR}
if [ $? -ne 0 ]; then
echo "ERROR. Could not update ${kbranch}"
exit 1
fi
# executes and modifies the source tree as required
patchme ${kbranch}
if [ $? -ne 0 ]; then
echo "ERROR. Could not modify ${kbranch}"
exit 1
fi
NOTE: Error expanding variable do_patch
ERROR: Please set SRCREV to a valid value while parsing
/home/dvhart/source/poky.git/meta/recipes-kernel/linux/linux-yocto-stable_git.bb
NOTE: Handling BitBake files: / (0311/0760) [40 %]NOTE: <class
'bb.fetch.InvalidSRCREV'>:Please set SRCREV to a valid value while
evaluating:
${@bb.fetch.get_srcrev(d)}
Thanks,
--
Darren Hart
Yocto Linux Kernel
next prev parent reply other threads:[~2010-12-09 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 14:35 [PATCH 0/3] linux-yocto: refactor recipes and update the kernel Bruce Ashfield
2010-12-08 14:35 ` [PATCH 1/3] yocto-kernel: factor common routes, update to 2.6.37 and branch renaming Bruce Ashfield
2010-12-08 20:20 ` Bruce Ashfield
2010-12-08 21:17 ` Bruce Ashfield
2010-12-09 1:31 ` Darren Hart
2010-12-08 20:49 ` Bruce Ashfield
2010-12-09 20:49 ` Darren Hart [this message]
2010-12-09 20:53 ` Bruce Ashfield
2010-12-10 1:33 ` Bruce Ashfield
2010-12-08 14:35 ` [PATCH 2/3] linux-libc-headers-yocto: use common linux-yocto routines Bruce Ashfield
2010-12-08 14:35 ` [PATCH 3/3] qemu: update arm timer handling Bruce Ashfield
2010-12-08 19:05 ` [PATCH 0/3] linux-yocto: refactor recipes and update the kernel Bruce Ashfield
2010-12-09 15:56 ` Bruce Ashfield
2010-12-09 18:34 ` Elizabeth Flanagan
-- strict thread matches above, loose matches on Subject: below --
2010-12-10 16:02 Bruce Ashfield
2010-12-10 16:02 ` [PATCH 1/3] yocto-kernel: factor common routes, update to 2.6.37 and branch renaming Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0140C4.5030603@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.