All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Tricca <flihp@twobit.us>
To: Yocto Project <yocto@yoctoproject.org>
Subject: native recipe and sysroot-destdir troubles
Date: Thu, 12 Apr 2012 10:44:56 -0400	[thread overview]
Message-ID: <4F86EA68.1070504@twobit.us> (raw)

Yocto,

I'm working on two new recipes and both are working quite well.  Now I
need native variants and online sources indicate this should be done
through BBCLASSEXTEND = "native".  For one of my recipes this works
fine, for the other not so much.

The error I'm seeing seems to be in the staging of the sysroot-destdir
which ends up being empty though the source code builds fine (image
directory has everything expected). do_populate_sysroot seems to assume
there's a directory structure present which ends up being empty causing
an error when it trys to tar the directory up.  If I create the
directories do_populate_sysroot expects the recipe runs to completion
but sysroot-destdir still ends up being empty and no packages are built.

Given that one of my packages works fine I'd guess the problem lies in
the Makefiles for the offending source tree and not yocto though I'm
still unsure of how to move forward.  Any help would be appreciated.  I
can pastebin the receips if that will help.

TIA,
- Philip

P.S. OE Build Configuration:
BB_VERSION        = "1.13.3"
TARGET_ARCH       = "i586"
TARGET_OS         = "linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "1.1"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta
meta-yocto        = "<unknown>:<unknown>"



             reply	other threads:[~2012-04-12 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 14:44 Philip Tricca [this message]
2012-04-12 23:55 ` native recipe and sysroot-destdir troubles Philip Tricca
2012-04-13 21:17   ` Philip Tricca
2012-04-15 11:26     ` Richard Purdie

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=4F86EA68.1070504@twobit.us \
    --to=flihp@twobit.us \
    --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.