From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: invalid recipe or a bug in bitbake?
Date: Wed, 09 Nov 2011 08:41:21 -0800 [thread overview]
Message-ID: <4EBAAD31.7040603@linux.intel.com> (raw)
In-Reply-To: <20111109130424.GB31478@deadlock.dhs.org>
On 11/09/2011 05:04 AM, Sergey 'Jin' Bostandzhyan wrote:
> Hi,
>
> I was trying to buld a simple native-only recipe and ran into a strange
> problem that can be triggered using theattached test recipe.
>
> The actual problem is that do_populate_sysroot fails, although I do not
> do anything in regard to that in my recipe, I only have a custom do_install.
>
> I do not see what I could be doing wrong in the recipe itself, it looks valid
> to me... but it always triggers the error where tar is getting wrong directories
> as parameters.
>
> I did look into sysroot_stage_dirs() in staging.bbclass, it's basically
> doing things like:
> sysroot_stage_dir $from${includedir} $to${includedir}
>
> My $from and $to seem to be correct, but the appended dirs seem to be wrong.
> I did echo ${includedir} and ${includedir_native} in my do_install() in the
> recipe, and it looked OK there...
>
I understand you solved your problem, but I have a follow-up
question/comment for you.
Based on your solution, it would be interesting to see the output of
bitbake -e native-test both before and after your change to to adding
the "/" and also the BBCLASSEXTEND change.
I do not think that the BBCLASSEXTEND change is correct, since you do
really only want a native built not a target and native.
You should just be using ${includedir} directly in your do_install()
since the native.bbclass fixes the ${exec_prefix} which ${includedir} uses.
Give that a try and you can use bitbake -e to check the variables.
Sau!
> I did build quite a few packages in this setup already, so it seems that my
> overall configuration is OK (setup is based angstrom 2010).
>
> I am using OE core with bitbake:
> BitBake Build Tool Core version 1.13.3, bitbake version 1.13.3
>
> Any ideas?
>
> Kind regards,
> Jin
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-11-09 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 13:04 invalid recipe or a bug in bitbake? Sergey 'Jin' Bostandzhyan
2011-11-09 15:38 ` Sergey 'Jin' Bostandzhyan
2011-11-09 16:11 ` Sergey 'Jin' Bostandzhyan
2011-11-09 16:41 ` Saul Wold [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=4EBAAD31.7040603@linux.intel.com \
--to=sgw@linux.intel.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