All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Problems building live image
Date: Mon, 14 Mar 2016 06:16:55 +0100	[thread overview]
Message-ID: <56E64947.5020606@mlbassoc.com> (raw)

I'd like to to some testing that qemu just doesn't seem up to
so I attempted to build a live ISO per the documentation. I
added these lines to local.conf:
   IMAGE_FSTYPES_genericx86 += "live"
   NOISO_genericx86 = "0"

When I try to build core-image-base I get this error:
   ERROR: INITRD_IMAGE_LIVE core-image-minimal-initramfs cannot use image live, hddimg or iso.
   ERROR: Check IMAGE_FSTYPES and INITRAMFS_FSTYPES settings.
   ERROR: Failed to parse recipe: /local/poky-cutting-edge/meta/recipes-core/images/core-image-minimal-initramfs.bb

I'm using a recent Poky checkout (d53413d3a8444c38a83ea37867c8af7754d8e702)

Am I just doing something wrong here? I was following this section of the mega-manual:

   26.56. image-live.bbclass¶

   The image-live class supports building "live" images.

   Normally, you do not use this class directly. Instead, you add "live" to IMAGE_FSTYPES.
   For example, if you were building an ISO image, you would add "live" to IMAGE_FSTYPES,
   set the NOISO variable to "0" and the build system would use the image-live class to
   build the ISO image.

I don't have any available hardware for this testing, so I thought
I'd use VirtualBox.  Is this a reasonable approach?  I want to use
a live ISO so I get a writable file system.  I tried just using the
.hddimage but that doesn't boot with VirtualBox :-(

To be clear, along with the additions above in local.conf, I tried:
   $ MACHINE=genericx86 bitbake core-image-base

Thanks for any ideas

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2016-03-14  5:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  5:16 Gary Thomas [this message]
2016-03-14  6:09 ` Problems building live image Khem Raj
2016-03-14 20:55   ` K Richard Pixley
2016-03-14 22:58     ` Rudolf Streif
2016-03-14 23:38       ` K Richard Pixley
2016-03-17 15:38         ` Rudolf J Streif
2016-03-14 16:34 ` K Richard Pixley
2016-03-14 17:01   ` Gary Thomas
2016-03-14 17:07     ` Khem Raj
2016-03-14 17:11       ` K Richard Pixley
2016-03-14 17:16         ` Khem Raj
2016-03-14 17:23           ` K Richard Pixley
  -- strict thread matches above, loose matches on Subject: below --
2016-03-14 17:29 Radzykewycz, T (Radzy)

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=56E64947.5020606@mlbassoc.com \
    --to=gary@mlbassoc.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.