From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Building images without kernel
Date: Thu, 5 Apr 2018 11:30:06 +0200 [thread overview]
Message-ID: <94d6aabf-f2a9-95c1-3827-6da3975f8936@siemens.com> (raw)
Hi,
my use-case is creating nfs root file systems with isar, so I don't need
the kernel created by isar. That worked with older isar version.
Now we have a strong dependency to some kernel.
Using my multiconfig it currently complains about:
Nothing PROVIDES 'linux-image-${KERNEL_NAME}'
Sure I can just set `KERNEL_IMAGE` to something, but wouldn't that then
deploy the kernel to my rfs?
Cheers,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next reply other threads:[~2018-04-05 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 9:30 Claudius Heine [this message]
2018-04-05 9:40 ` Jan Kiszka
2018-04-05 9:54 ` 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=94d6aabf-f2a9-95c1-3827-6da3975f8936@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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