All of lore.kernel.org
 help / color / mirror / Atom feed
From: JH <jupiter.hce@gmail.com>
To: Ferry Toth <fntoth@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<public-openembedded-core-ZwoEplunGu3dfDuKDZ/zN51Ccm5ICvs9@plane.gmane.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: Failed to build zImage-initramfs
Date: Sun, 20 Oct 2019 20:20:14 +1100	[thread overview]
Message-ID: <CAA=hcWSWWWZH1fbrKdZZUUrza7DkhwbguvQjd5AbBPt_Jk3nCg@mail.gmail.com> (raw)
In-Reply-To: <a4ef22e6-7c12-027a-b1cd-fa807fcfccb8@gmail.com>

Thanks Ferry and Khem,

Finally built the zImage-initramfs, but it does not bundle the rootfs,
how can I included the rootfs to the zImage?

There is n old style link in  kernel.bbclass:
use_alternate_initrd=CONFIG_INITRAMFS_SOURCE=${B}/usr/${INITRAMFS_IMAGE_NAME}.cpio

I think there is some new way to do it, what relevent kernel setup
variables need be defined?

Thank you.

Kind regards,

- jh

On 10/13/19, Ferry Toth <fntoth@gmail.com> wrote:
> Hi
>
> Op 13-10-19 om 11:10 schreef JH:
>> On 10/13/19, Khem Raj <raj.khem@gmail.com> wrote:
>>
>>>> $ vi local.conf
>>>> IMAGE_ROOTFS += " core-image-minimal-initramfs"
>>>>
>>>
>>> INITRAMFS_IMAGE should be an image name. Like core-image-minimal or
>>> somesuch
>>
>> Hmm, change it to my image, the name is solar-image.bb (bitbake
>> solar-image), is it correct to change it in my local.conf as per your
>> instruction?
>>
>> $ vi local.conf
>> INITRAMFS_IMAGE = "solar-image"
>>
>> That caused circular dependecies. Without specifying INITRAMFS_IMAGE,
>> my build was all fine, as soon as add INITRAMFS_IMAGE, it's first
>> error was "Nothing RPROVIDES", I must miss things here.
>>
>> ERROR: These are usually caused by circular dependencies and any
>> circular dependency chains found will be printed below. Increase the
>> debug level to see a list of unbuildable tasks.
>> ERROR:
>> Dependency loop #1 found:
>>    Task
>> /build/Ramdisk/oe-core/../meta-solar/recipes-core/images/solar-image.bb:do_image_complete
>> (dependent Tasks ['solar-image.bb:do_image_cpio',
>> 'solar-image.bb:do_image_wic', 'solar-image.bb:do_image',
>> 'solar-image.bb:do_image_tar'])
>>    Task
>> /build/Ramdisk/oe-core/../meta-solar/recipes-kernel/linux/linux-solar_4.19.bb:do_bundle_initramfs
>> (dependent Tasks ['solar-image.bb:do_image_complete',
>> 'linux-solar_4.19.bb:do_install'])
>>    Task
>> /build/Ramdisk/oe-core/../meta-solar/recipes-kernel/linux/linux-solar_4.19.bb:do_deploy
>> (dependent Tasks ['linux-solar_4.19.bb:do_packagedata',
>> 'depmodwrapper-cross_1.0.bb:do_populate_sysroot',
>> 'linux-solar_4.19.bb:do_bundle_initramfs',
>> 'linux-solar_4.19.bb:do_populate_sysroot',
>> 'linux-solar_4.19.bb:do_assemble_fitimage_initramfs'])
>>    Task
>> /build/Ramdisk/oe-core/../meta-solar/recipes-core/images/solar-image.bb:do_image_wic
>> (dependent Tasks ['linux-solar_4.19.bb:do_deploy',
>> 'u-boot-imx_2017.03.bb:do_deploy',
>> 'gptfdisk_1.0.4.bb:do_populate_sysroot',
>> 'dosfstools_4.1.bb:do_populate_sysroot',
>> 'mtools_4.0.18.bb:do_populate_sysroot',
>> 'solar-image.bb:do_rootfs_wicenv', 'solar-image.bb:do_image',
>> 'parted_3.2.bb:do_populate_sysroot'])
>>
>>
>> ERROR: Command execution failed: 1
>
> As an example you might want to look at my repo, I have 2 images minimal
> and initramfs:
> https://github.com/edison-fw/meta-intel-edison/tree/master/meta-intel-edison-distro/recipes-core/images
>
>
>>
>> Thank you very much Khem,
>>
>> Kind regards,
>>
>>   - jh
>>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>


      reply	other threads:[~2019-10-20  9:20 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
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 [this message]

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='CAA=hcWSWWWZH1fbrKdZZUUrza7DkhwbguvQjd5AbBPt_Jk3nCg@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --cc=fntoth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=public-openembedded-core-ZwoEplunGu3dfDuKDZ/zN51Ccm5ICvs9@plane.gmane.org \
    --cc=raj.khem@gmail.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 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.