From: Khem Raj <raj.khem@gmail.com>
To: JH <jupiter.hce@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: Failed to build zImage-initramfs
Date: Sat, 12 Oct 2019 18:24:33 -0700 [thread overview]
Message-ID: <ce141cece91f76d77a7316394ecd9c8776e4b257.camel@gmail.com> (raw)
In-Reply-To: <CAA=hcWSN3s3YGNrods9t2bRsAbwVf1x1fRXDofVgjtr-BK29Bg@mail.gmail.com>
On Sun, 2019-10-13 at 12:14 +1100, JH wrote:
> Hi,
>
> Apologize if it is not right mailing list for helps, please advise
> which mailing list I should go.
>
> I have been trying to build zImage-initramfs, according to the
> oe-core/meta/classes/kernel.bbclass, I defined following variables in
> local.conf:
>
> INITRAMFS_IMAGE = "zImage-initramfs"
this should be the rootfs image that you want to bundle into kernel and
not the name of final kernel as above. Put something like core-image-
minimal-initramfs or somesuch here.
> INITRAMFS_IMAGE_NAME = "zImage-initramfs"
> INITRAMFS_IMAGE_BUNDLE = "1"
> IMAGE_INSTALL_append = "zImage-initramfs"
>
> But I had following errors:
>
> ERROR: Nothing RPROVIDES 'zImage-initramfs' (but
> /build/Ramdisk/oe-core/../meta-solar/recipes-core/images/ram-image.bb
> RDEPENDS on or otherwise requires it)
>
> NOTE: Runtime target 'zImage-initramfs' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['zImage-initramfs']
>
> ERROR: Required build target 'solar-image' has no buildable
> providers.
> Missing or unbuildable dependency chain was: ['ram-image', 'zImage-
> initramfs']
>
> In my ram-image.bb:
>
> inherit core-image
>
> IMAGE_ROOTFS_SIZE = "100000"
> IMAGE_FSTYPES += " ${INITRAMFS_FSTYPES} cpio.gz tar.gz"
> PACKAGE_INSTALL = "${IMAGE_INSTALL}"
>
> What I am missing for "Nothing RPROVIDES" error?
>
> Thank you.
>
> Kind regards,
>
> - jh
next prev parent reply other threads:[~2019-10-13 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 1:14 Failed to build zImage-initramfs JH
2019-10-13 1:24 ` Khem Raj [this message]
2019-10-13 4:06 ` JH
2019-10-13 5:09 ` Khem Raj
2019-10-13 9:10 ` JH
2019-10-13 10:32 ` Ferry Toth
2019-10-20 9:20 ` JH
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=ce141cece91f76d77a7316394ecd9c8776e4b257.camel@gmail.com \
--to=raj.khem@gmail.com \
--cc=jupiter.hce@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox