All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Rush <jeff@taupro.com>
To: openembedded-devel@lists.openembedded.org
Subject: rootfs_tar.bbclass not found?
Date: Tue, 19 May 2009 09:03:24 -0500	[thread overview]
Message-ID: <4A12BC2C.5020402@taupro.com> (raw)

Hopefully a trivial question.

Objective: I am trying to generate a tarball of an executable program, the
helloworld.bb program, for installation onto a system that lacks support for
ipk files.

To get a tarball package, I add to my local.conf:

   INHERIT += "package_tar package_ipk"

but when I do:

   bitbake helloworld

or indeed any target, I get the following error during the parse stage:

ERROR: Could not inherit file classes/rootfs_tar.bbclass while parsing
/home/jeff/Projects/OpenEmbedded/openembedded/recipes/images/slugos-image.bb

This error is repeated for every *-image.bb file parsed.  The reason is
because the file classes/image.bbclass has this line at the top of the file:

  inherit rootfs_${IMAGE_PKGTYPE}

so it is looking for "rootfs_tar.bbclass" but the only rootfs-*.bbclass files
that exist are:

  classes/rootfs_deb.bbclass
  classes/rootfs_ipk.bbclass
  classes/rootfs_rpm.bbclass

So building an image from tar'd packages is not support - fine, because in
this case I really do not want to build an image, just a single helloworld.tar
package.  But I cannot get past the parsing phase because of this problem.

What can I add to my local.conf to 'short circuit' this logic related to the
building of images?

Thanks for helping out a newbie,

-Jeff



             reply	other threads:[~2009-05-19 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 14:03 Jeff Rush [this message]
2009-05-20  0:25 ` rootfs_tar.bbclass not found? Denys Dmytriyenko
2009-05-20  5:58   ` Jeff Rush

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=4A12BC2C.5020402@taupro.com \
    --to=jeff@taupro.com \
    --cc=openembedded-devel@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 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.