The 3.0 pull request was held up behind 3.2 work. But I just pushed out a meta branch update that contained: commit f1ef128bff854ce2614e655283ecca92d22f0b88 Author: Bruce Ashfield

Hi Bruce, Could you please let me know if the fix is available for this? Thanks Kishore.

From my experience, this is true. Regardless of the SRCI_URI, the downloads directory contains everything that poky/bitbake need to do builds after the initial fetch has been performed. And

What kind of errors? Some details might help understand what the problem is. I think so, but I'm not 100% sure. The way I have my system set up, I never download anything more than once :-) I have

I'm not sure it does. I don't want poky to do more work. I have my download directory, $DL_DIR, outside my build directory so I can keep it run to run, as mentioned in the comments in local.conf. I

Queued. Bruce

The beagle board would be building on the branch listed in the meta-yocto layer. KMACHINE_beagleboard = "yocto/standard/beagleboard" Everything that you've done is fine, but pushing your changes

OK, hate to bring this up again but I must be doing something wrong. My kernel changes don't appear to be getting picked up. I thought it was OK before but then I did some real work on the kernel and

If you set BB_GENERATE_MIRROR_TARBALLS = "1" (e.g. in local.conf) then you'll get tarballs which hold the git repositories after download. You can then reuse these (by sharing the DL_DIR or using a

I have used both git and the tarball methods of bitbaking projects, all of them derivatives of the examples in the Yocto documentation. I was having issues using the local clone of the Yocto kernel

nothing is broken. Its the mono package which uses older version of libtool (pre 2.4) and its trying to link in .la files which are generated by new libtool 2.4+ your best option is that add the mono

Hi Mark! I set up the custom layer following your suggestions and it's building now... By inspecting the logs I see "-march=i486" applied to compiler's command lines. I won't be able to test the

Agenda   * Opens collection - 5 min (Song) * Yocto 1.1.1 point release update - 10 min (Josh/Beth) * Yocto 1.2 M2 status, M3 planning status - 10 min

Jim Abernathy Looks good to me.

<paul.eggleton@...> wrote: I have created a new link titled "How Do I" on the main page and for now, this is the only entry. Please take a

So I would say if any of our documentation is out-of-date or unclear, it should be fixed, no deliberation needed :) However, in Poky master, README.hardware has now been updated to remove

A few things you will need.. a tune file for the CPU, and a tune file for the machine/bsp... and you'll have to make sure that eglibc/Linux can still run on that machine. I know a while back some

Excellent question, Jack - we are working on that this week. No promises, but highly likely!

Yup, I wrote then off the cuff, I am glad that a typo is the only error and no major missing steps :-) I am also glad that these steps worked for you. I have not. I am not sure I should. I am not

This worked fine for me. one typo in step (5) ext3 and not text3, but these are good instructions. How do we get them put into the README.hardware instead of the directdisk section that doesn't work