On Wed, Jan 23, 2013 at 8:05 AM, Patrick Turley
wrote:
> Here's our machine in local.conf:
>
> MACHINE = "dm8148-mpu"
>
> Naturally, then, we see a directly like this under tmp/work:
>
> dm8148_mpu-poky-linux-gnueabi
This will contain builds of machine specific packages
>
> Also, under t
On Jan 23, 2013, at 10:19 AM, "Zhang, Jessica" wrote:
> Please file a bug at bugzilla.yoctoproject.org
Done:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3784
Thank you.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproje
On Jan 23, 2013, at 10:21 AM, Khem Raj
mailto:raj.k...@gmail.com>> wrote:
Did you source the env script before doing all that ?
Thank you for your question, but it doesn't apply. All of this happens
*before* I even tried to build anything.
The fundamental problem is that the SDK installation
Did you source the env script before doing all that ?
On Wednesday, January 23, 2013, Patrick Turley
wrote:
> Here's our machine in local.conf:
>
> MACHINE = "dm8148-mpu"
>
> Naturally, then, we see a directly like this under tmp/work:
>
> dm8148_mpu-poky-linux-gnueabi
>
> Also, under tmp
in the SDK
Here's our machine in local.conf:
MACHINE = "dm8148-mpu"
Naturally, then, we see a directly like this under tmp/work:
dm8148_mpu-poky-linux-gnueabi
Also, under tmp/sysroots, we see these two:
dm8148-mpu
dm8148-mpu-tcbootstrap
Finally, when I install
Here's our machine in local.conf:
MACHINE = "dm8148-mpu"
Naturally, then, we see a directly like this under tmp/work:
dm8148_mpu-poky-linux-gnueabi
Also, under tmp/sysroots, we see these two:
dm8148-mpu
dm8148-mpu-tcbootstrap
Finally, when I install the SDK, I see the followi
