From: Francesco <fdprnd@dave.eu>
To: isar-users@googlegroups.com
Subject: default image won't build
Date: Wed, 18 Apr 2018 12:50:39 +0200 [thread overview]
Message-ID: <e50c604e-31c9-1d84-1370-aa3596778950@dave.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4149 bytes --]
Hello everyone,
I'm new to isar and today I made an attempt to build the default image
with it. I installed all the host tools necessary as it is written in
the docs. Then I followed strictly the doc/user_manual.
My host OS is debian jessie.
Unfortunately when I try to build an image I get this error:
/bitbake isar-image-base//
//Parsing recipes: 100%
|###########################################################################################################################################|
Time: 0:00:00//
//Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0
skipped, 0 masked, 0 errors.//
//NOTE: Resolving any missing task queue dependencies//
//ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but
/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb
DEPENDS on or otherwise requires it)//
//ERROR: Required build target 'isar-image-base' has no buildable
providers.//
//Missing or unbuildable dependency chain was: ['isar-image-base',
'linux-image-${KERNEL_NAME}']/
So I added KERNEL_NAME ?= "armmp" to the local.conf but now I get
another error:
/bitbake isar-image-base//
//Parsing recipes: 100%
|###########################################################################################################################################|
Time: 0:00:00//
//Parsing of 11 .bb files complete (0 cached, 11 parsed). 110 targets, 0
skipped, 0 masked, 0 errors.//
//NOTE: Resolving any missing task queue dependencies//
//ERROR: Nothing PROVIDES 'linux-image-${KERNEL_NAME}' (but
/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb
DEPENDS on or otherwise requires it)//
//ERROR: Required build target 'isar-image-base' has no buildable
providers.//
//Missing or unbuildable dependency chain was: ['isar-image-base',
'linux-image-${KERNEL_NAME}']//
//
//
//bitbake isar-image-base//
//Loading cache: 100%
|#############################################################################################################################################|
Time: 0:00:00//
//Loaded 110 entries from dependency cache.//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//NOTE: Resolving any missing task queue dependencies//
//Initialising tasks: 100%
|########################################################################################################################################|
Time: 0:00:00//
//NOTE: Executing RunQueue Tasks//
//ERROR: isar-image-base-1.0-r0 do_rootfs: Function failed: do_rootfs
(log file is located at
/mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
//ERROR: Logfile of failure stored in:
/mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481//
//Log data follows://
//| DEBUG: Executing shell function do_rootfs//
//| sudo: no tty present and no askpass program specified//
//| WARNING: exit code 1 from a shell command.//
//| ERROR: Function failed: do_rootfs (log file is located at
/mnt/elbe/Isar/build/tmp/work/debian-jessie-armhf/isar-image-base/temp/log.do_rootfs.12481)//
//ERROR: Task
(/mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs)
failed with exit code '1'//
//NOTE: Tasks Summary: Attempted 6 tasks of which 5 didn't need to be
rerun and 1 failed.//
//
//Summary: 1 task failed://
///mnt/elbe/Isar/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs//
//Summary: There was 1 ERROR message shown, returning a non-zero exit
code.//
/
the default tty in the conf/machine for qemuarm is set to ttyAMA0. My
user is in the sudoers file as showed in the docs. I don't understand
what I'm doing wrong here.
Hope you can help.
Frank
[-- Attachment #2: Type: text/html, Size: 5441 bytes --]
next reply other threads:[~2018-04-18 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 10:50 Francesco [this message]
2018-04-18 10:56 ` Jan Kiszka
2018-04-18 11:01 ` Claudius Heine
2018-04-18 11:03 ` Jan Kiszka
2018-04-18 11:08 ` Francesco
2018-04-18 11:15 ` Claudius Heine
2018-04-18 12:12 ` Francesco
2018-04-18 11:01 ` Alexander Smirnov
2018-04-18 11:14 ` Alexander Smirnov
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=e50c604e-31c9-1d84-1370-aa3596778950@dave.eu \
--to=fdprnd@dave.eu \
--cc=isar-users@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox