some potential fixes for poky reference manual, i'll graciously
allow scott rifenbark to do all the work. :-)
working in appendix F (variable glossary):
* INITSCRIPT_PACKAGES: it seems that it's not only if there are
multiple packages that you'll need to append the package names to
subseque
> But do note that if you ship libstdc++ without anything linking to it you
> forego on the linking
> exception to the GPL. That is general is a Very Bad Thing(TM), so ship a
> helloword.cpp
> binary to keep the fsf happy. As an added bonus the helloworld will drag in
> the lib automatically.
On 06/28/2012 03:44 AM, Tomas Frydrych wrote:
Hi Koen,
On 27/06/12 22:58, Koen Kooi wrote:
I have no problem with poky-the-distro, I have a problem with
poky-the-buildsystem. I warned mallum about this confusion years ago,
but you know how stubborn he can be :)
The Yocto naming confusion is e
Just curious if anyone here has run yocto images using MACHINE=beagleboard on
qemu. And if so, did you get networking working?
Right now I'm just working with the stock denzil release, not the meta-ti layer
yet. I did manage to get this running on Qemu (from what I can tell from web
search, t
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 u
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
