On 19 April 2013 17:23, Saul Wold s...@linux.intel.com wrote:
Just another note about the netbase, for 1.4 the interfaces file moved to
init-ifupdown, so that file should move to a new recipe with bbappends for
init-ifupdown-1.0.
We just fixed meta-yocto for the beagleboard in the final 1.4
On Sat, 2013-04-20 at 05:35 -0400, Robert P. J. Day wrote:
On Fri, 19 Apr 2013, Tom Zanussi wrote:
On Fri, 2013-04-19 at 08:37 -0400, Robert P. J. Day wrote:
second, the BBLAYERS example there seems overly complicated and
potentially confusing to beginners. the fact that meta-yocto
Hello,
When I was trying to build yocto for the i.mx6, there was an error building
busybox. The error when building busbox was
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
|
On Sat, Apr 20, 2013 at 4:05 PM, Paul Barker p...@paulbarker.me.uk wrote:
On 19 April 2013 17:23, Saul Wold s...@linux.intel.com wrote:
Just another note about the netbase, for 1.4 the interfaces file moved to
init-ifupdown, so that file should move to a new recipe with bbappends
for
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this
recipe remainder until newer
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
