From: "Andreas Müller" <schnitzeltony@gmx.de>
To: meta-ti@yoctoproject.org
Subject: Re: [PATCH 1/5] linux.inc: If the kernel has CONFIG_KERNEL_LZO=y, it may well attempt to use the 'lzop' utility to do the lzo compression, but we should not be relying on that utility being installed on the build machine.
Date: Tue, 20 Dec 2011 00:22:44 +0100 [thread overview]
Message-ID: <201112200022.45166.schnitzeltony@gmx.de> (raw)
In-Reply-To: <1324311340-16981-1-git-send-email-koen@dominion.thruhere.net>
On Monday, December 19, 2011 05:15:36 PM Koen Kooi wrote:
> From: Christopher Larson <chris_larson@mentor.com>
>
> This currently affects the linux-omap4 build for omap4430-panda.
>
> Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> recipes-kernel/linux/linux.inc | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux.inc
> b/recipes-kernel/linux/linux.inc index 9650e68..e8a754f 100644
> --- a/recipes-kernel/linux/linux.inc
> +++ b/recipes-kernel/linux/linux.inc
> @@ -264,3 +264,14 @@ pkg_postrm_kernel-devicetree () {
> cd /${KERNEL_IMAGEDEST}; update-alternatives --remove devicetree
> devicetree-${KERNEL_VERSION} || true }
>
> +# Automatically depend on lzop-native if CONFIG_KERNEL_LZO is enabled
> +python () {
> + try:
> + defconfig = bb.fetch2.localpath('file://defconfig', d)
> + except bb.fetch2.FetchError:
> + pass
> + else:
> + if 'CONFIG_KERNEL_LZO=y\n' in open(defconfig).readlines():
> + depends = d.getVar('DEPENDS', False)
> + d.setVar('DEPENDS', depends + ' lzop-native')
> +}
I am afraid since this patch I get
ERROR: Unable to parse /home/Superandy/data/oe-core/sources/meta-ti/recipes-
kernel/linux/linux_3.1.bb########################
| ETA: 00:00:00
Traceback (most recent call last):
File "/home/Superandy/oe-core/sources/bitbake/lib/bb/parse/ast.py", line 379,
in multi_finalize(fn='/home/Superandy/data/oe-core/sources/meta-ti/recipes-
kernel/linux/linux_3.1.bb', d=<bb.data_smart.DataSmart object at 0x6e5e390>):
try:
> finalize(fn, d)
except bb.parse.SkipPackage as e:
File "/home/Superandy/oe-core/sources/bitbake/lib/bb/parse/ast.py", line 323,
in finalize(fn='/home/Superandy/data/oe-core/sources/meta-ti/recipes-
kernel/linux/linux_3.1.bb', d=<bb.data_smart.DataSmart object at 0x6e5e390>,
variant=None):
code.append("%s(d)" % funcname)
> bb.utils.simple_exec("\n".join(code), {"d": d})
bb.data.update_data(d)
File "/home/Superandy/oe-core/sources/bitbake/lib/bb/utils.py", line 387, in
simple_exec(code='__anon_119__home_Superandy_data_oe_core_sources_openembedded_core_meta_classes_staging_bbclass(d)\n__anon_487__home_Superandy_data_oe_core_sources_openembedded_core_meta_classes_base_bbclass(d)\n__anon_20__home_Superandy_data_oe_core_sources_openembedded_core_meta_classes_debian_bbclass(d)\n__anon_19__home_Superandy_data_oe_core_sources_meta_openembedded_meta_oe_classes_blacklist_bbclass(d)\n__anon_189__home_Superandy_data_oe_core_sources_openembedded_core_meta_classes_package_bbclass(d)\n__anon_55__home_Superandy_data_oe_core_sources_openembedded_core_meta_classes_sstate_bbclass(d)\n__anon_447__home_Superandy_data_oe_core_sources_openembedded_core_meta_classes_package_ipk_bbclass(d)\n__anon_28__home_Superandy_data_oe_core_sources_meta_openembedded_meta_oe_classes_kernel_bbclass(d)\n__anon_119__home_Superandy_data_oe_core_sources_openembedded_core_meta_classes_siteinfo_bbclass(d)\n__anon_72__home_Superandy_data_oe_core_sources_meta_ti_recipes_kernel_linux_linux_inc(d)\n__anon_277__home_Superandy_data_oe_core_sources_meta_ti_recipes_kernel_linux_linux_inc(d)',
context={'d': <bb.data_smart.DataSmart object at 0x6e5e390>}):
def simple_exec(code, context):
> exec(code, _context, context)
File "<string>", line 11, in <module>
File
"__anon_277__home_Superandy_data_oe_core_sources_meta_ti_recipes_kernel_linux_linux_inc",
line 7, in
__anon_277__home_Superandy_data_oe_core_sources_meta_ti_recipes_kernel_linux_linux_inc(d=<bb.data_smart.DataSmart
object at 0x6e5e390>)
IOError: [Errno 2] No such file or directory:
'/home/Superandy/data/Downloads/packets/dl/defconfig'
Hints:
* reverting fixed issue
* /home/Superandy/data/Downloads/packets/dl is my download directory
Andreas
prev parent reply other threads:[~2011-12-19 23:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 16:15 [PATCH 1/5] linux.inc: If the kernel has CONFIG_KERNEL_LZO=y, it may well attempt to use the 'lzop' utility to do the lzo compression, but we should not be relying on that utility being installed on the build machine Koen Kooi
2011-12-19 16:15 ` [PATCH 2/5] ti-xdctools: update to 3.23.00.32 Koen Kooi
2011-12-19 19:40 ` Denys Dmytriyenko
2011-12-27 3:00 ` Peter Bigot
2011-12-19 16:15 ` [PATCH 3/5] ti-dspbios: update to 5.41.11.38 Koen Kooi
2011-12-19 19:41 ` Denys Dmytriyenko
2011-12-19 16:15 ` [PATCH 4/5] ti-ipc: update to 1_24_00_16 Koen Kooi
2011-12-19 19:42 ` Denys Dmytriyenko
2011-12-19 16:15 ` [PATCH 5/5] ti-sysbios: add 6.33.00.19 Koen Kooi
2011-12-19 19:42 ` Denys Dmytriyenko
2011-12-19 19:37 ` [PATCH 1/5] linux.inc: If the kernel has CONFIG_KERNEL_LZO=y, it may well attempt to use the 'lzop' utility to do the lzo compression, but we should not be relying on that utility being installed on the build machine Denys Dmytriyenko
2011-12-19 23:22 ` Andreas Müller [this message]
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=201112200022.45166.schnitzeltony@gmx.de \
--to=schnitzeltony@gmx.de \
--cc=meta-ti@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.