From: Gary Thomas <gary@mlbassoc.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: [meta-fsl-arm] Missing host dependency for 3.10 kernel?
Date: Thu, 03 Apr 2014 05:44:58 -0600 [thread overview]
Message-ID: <533D49BA.4030501@mlbassoc.com> (raw)
I just tried to build the 3.10+ kernel for my SabreLite board
and got this error:
LZO arch/arm/boot/compressed/piggy.lzo
/bin/sh: lzop: command not found
make[2]: *** [arch/arm/boot/compressed/piggy.lzo] Error 1
make[2]: *** Waiting for unfinished jobs....
CC arch/arm/boot/compressed/misc.o
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [uImage] Error 2
ERROR: oe_runmake failed
WARNING: /home/local/imx6_2014-04-02/tmp/work/nitrogen6x-amltd-linux-gnueabi/linux-boundary/3.10.17-r0/temp/run.do_compile.17300:1 exit 1 from
exit 1
ERROR: Function failed: do_compile (log file is located at /home/local/imx6_2014-04-02/tmp/work/nitrogen6x-amltd-linux-gnueabi/linux-boundary/3.10.17-r0/temp/log.do_compile.17300)
It seems that the 'lzop' program (a new one on me) is not installed
on any of my build hosts.
Shouldn't this be handled by the Yocto build system using either
a sanity requirement or native package to provide the tool?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2014-04-03 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 11:44 Gary Thomas [this message]
2014-04-03 13:38 ` [meta-fsl-arm] Missing host dependency for 3.10 kernel? Erik Botö
2014-04-03 14:16 ` [meta-fsl-arm-extra][PATCH] linux-boundary: Add DEPENDS on lzop Eric Nelson
2014-04-03 14:17 ` [meta-fsl-arm] Missing host dependency for 3.10 kernel? Eric Nelson
2014-04-03 14:35 ` Gary Thomas
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=533D49BA.4030501@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@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.