From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Updating daisy -> Python.h not found
Date: Fri, 17 Oct 2014 17:01:46 +0200 [thread overview]
Message-ID: <m1rb0r$ucm$1@ger.gmane.org> (raw)
In-Reply-To: <9690622.nYuOPMAxm8@peggleto-mobl5.ger.corp.intel.com>
Am 17.10.2014 um 16:51 schrieb Paul Eggleton:
> Hi there,
>
> I agree this sort of thing shouldn't happen on a stable branch. I'm not sure
> what would have caused such a problem though. However, above you are looking
> under tmp/work, but the file being present under there doesn't really say much
> - the key question is is it still in the sysroot i.e. tmp/sysroots/* ? The
> first thing to figure out is if the file is really missing, or if it is now
> simply not looking for it in the right location.
>
> Cheers,
> Paul
>
Very good point.
$ find tmp/sysroots/ -name "Python.h"
tmp/sysroots/i686-linux/usr/include/python2.7/Python.h
tmp/sysroots/i686-linux/usr/include/python3.3m/Python.h
tmp/sysroots/cubox-i/usr/include/python2.7/Python.h
tmp/sysroots/cubox-i/usr/include/python3.3m/Python.h
So, it seems to be there, if I see that correctly. The question then
seems to be, why it is no longer found?
Thanks for you help, Paul.
Cheers
Michael
next prev parent reply other threads:[~2014-10-17 15:02 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 [this message]
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
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='m1rb0r$ucm$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.