From: Jaap de Jong <jaap.dejong@nedap.com>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: Kernel size above KERNEL_IMAGE_MAXSIZE
Date: Thu, 14 Dec 2017 12:21:58 +0100 [thread overview]
Message-ID: <e04717a8-e142-73f9-ebe2-5e7ffa5bc1fb@nedap.com> (raw)
Hi All,
not sure if I should put this here.
If I define KERNEL_IMAGE_MAXSIZE below my actual kernel size I get this
ugly error:
ERROR: linux-at91-4.9.28-r0.4 do_sizecheck: Function failed:
do_sizecheck (log file is located at
xxx/linux-at91/4.9.28-r0.4/temp/log.do_sizecheck.1370)
ERROR: Logfile of failure stored in:
xxx/linux-at91/4.9.28-r0.4/temp/log.do_sizecheck.1370
Log data follows:
| DEBUG: Executing shell function do_sizecheck
| xxx/linux-at91/4.9.28-r0.4/temp/run.do_sizecheck.1370: line 117: warn:
command not found
| WARNING: xxx/linux-at91/4.9.28-r0.4/temp/run.do_sizecheck.1370:1 exit
127 from 'warn "This kernel $type (size=$size(K) > 2100(K)) is too big
for your device. Please reduce the size of the kernel by making more of
it modular."'
| ERROR: Function failed: do_sizecheck (log file is located at
xxx/linux-at91/4.9.28-r0.4/temp/log.do_sizecheck.1370)
ERROR: Task
(xxx/meta-atmel/recipes-kernel/linux/linux-at91_4.9.bb:do_sizecheck)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1646 tasks of which 1638 didn't need to
be rerun and 1 failed.
Summary: 1 task failed:
xxx/meta-atmel/recipes-kernel/linux/linux-at91_4.9.bb:do_sizecheck
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Either poky/meta/classes/kernel.bbclass should be changed to run 'die'
instead of 'warn' or in poky/meta/classes/base.bbclass a function 'warn'
should be added. Not sure which. I tend to the first option: if the
kernel image is too large then this is an error.
Regards,
Jaap
reply other threads:[~2017-12-14 11:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e04717a8-e142-73f9-ebe2-5e7ffa5bc1fb@nedap.com \
--to=jaap.dejong@nedap.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.