Sorry for the previous message. Accidentally sent it out.
Thanks, Andre! That explains a lot.
I got rid of the entire tmp directory and then rebuilt. And unfortunately
I'm still running into the same problem...
I entered the directory shown in the error and did a 'file' on the
binaries. They are
Thanks, Andre! That explains a lot.
I got rid of the entire tmp directory and then rebuilt. And unfortunately
I'm still running into the same problem...
Looking at the error again (see below)
On Tue, Jun 6, 2017 at 1:30 PM, Andre McCurdy wrote:
> On Tue, Jun 6, 2017 at
On Tue, Jun 6, 2017 at 5:42 AM, Zhuoqun Cheng wrote:
> Hi Yocto Experts,
>
> I'm fairly new to Yocto and I've already tried my best to search for
> answers, but not happy with what I found.
>
> So here's the situation I've got:
>
> I'm using yocto to build the intel aero board image,
Hi Leo and Khem,
I just changed the MACHINE var to "intel-core2-32" (I assume it's the one
in build/conf/local.conf. It was read-only and I added write permission)
and it still gives me the same error.
Here's some info that might be useful, before I change, when I do build, it
prints:
Build
On Tue, 2017-06-06 at 08:42 -0400, Zhuoqun Cheng wrote:
> Hi Yocto Experts,
>
>
> I'm fairly new to Yocto and I've already tried my best to search for
> answers, but not happy with what I found.
>
>
> So here's the situation I've got:
>
>
> I'm using yocto to build the intel aero board
On Tue, Jun 6, 2017 at 5:42 AM, Zhuoqun Cheng wrote:
> Hi Yocto Experts,
>
> I'm fairly new to Yocto and I've already tried my best to search for
> answers, but not happy with what I found.
>
> So here's the situation I've got:
>
> I'm using yocto to build the intel aero board image,