From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Updating daisy -> Python.h not found
Date: Sat, 18 Oct 2014 10:51:30 +0200 [thread overview]
Message-ID: <m1t9ml$43g$1@ger.gmane.org> (raw)
In-Reply-To: <20141018084423.GB2437@jama>
Am 18.10.2014 um 10:44 schrieb Martin Jansa:
> On Sat, Oct 18, 2014 at 09:11:51AM +0200, Neuer User wrote:
>> I don't see any chance to get this running. The whole environment seems
>> to be missing, such as BUILD_SYS, HOST_SYS, STAGING_LIB_DIR and other.
>>
>> I will now completely resetup yocto from scratch, hoping that this fixes
>> the problem. Will report tomorrow or as soon as I have a result.
>
> Have you tried to revert these 2 changes?
> http://git.openembedded.org/openembedded-core/commit/?h=daisy&id=de5797b27a358954eb15318d0d77ad1981981861
> http://git.openembedded.org/openembedded-core/commit/?h=daisy&id=ae49adc13db10cb39eeb9377eb4c60a4db436e00
>
>
>
Thanks, they look very promising.
Currently I have completely set up my yocto environment from scratch
again. It's curently compiling. There was another error that due to some
metadata left from the older daisy version that I needed to fix by
cleaning the work dir. So maybe this is something similar here.
If that doesn't help, I will look into reverting these two changes.
Btw. do you know that the qt5 repo is currently incompatible with daisy?
There is a patch in fsl-arm that cannot be applied:
./meta-fsl-arm/qt5-layer/recipes-qt/qt5/qtmultimedia_%.bbappend
This needs to be deleted, otherwise qtmultimedia cannot be generated.
next prev parent reply other threads:[~2014-10-18 8:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 10:00 Updating daisy -> Python.h not found Neuer User
2014-10-17 14:51 ` Paul Eggleton
2014-10-17 15:01 ` Neuer User
2014-10-17 15:05 ` Paul Eggleton
2014-10-17 15:19 ` Neuer User
2014-10-17 16:09 ` Neuer User
2014-10-18 7:11 ` Neuer User
2014-10-18 8:44 ` Martin Jansa
2014-10-18 8:51 ` Neuer User [this message]
2014-10-18 9:10 ` Martin Jansa
2014-10-18 9:19 ` Neuer User
2014-10-18 9:36 ` Martin Jansa
2014-10-18 9:32 ` SOLUTION: " Neuer User
2014-10-18 10:03 ` Martin Jansa
2014-10-18 21:20 ` Tyler Hall
2014-10-18 21:33 ` Tyler Hall
2014-10-19 6:16 ` Neuer User
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='m1t9ml$43g$1@ger.gmane.org' \
--to=auslands-kv@gmx.de \
--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.