Hi Rudi, Good to hear that you’ve resolved your issue. For the kernel issue, would you mind to file a bug (enhancement) in our bugzilla for us to track? As to adt-installer, it is meant to be an

Hi Jessica, Thanks while responding while on vacation. No worries. I have resolved the NFS boot issue. I entirely missed that my dev system had a firewall running blocking ports 3048 and 3049 used by

Thanks for catching this, Rudolf. I've corrected this and have added a bug entry against the release scripts. -b -- Elizabeth Flanagan Yocto Project Build and Release

Hi Rudi, I’m currently on vacation so have very limited access to my YP setup. We’ve been using the sysroot and nfs like below to start qemu after adt-installation, can you give it a try to

its an option for libtool sysroot support actually it was called --with-sysroot but it conflicts with gcc and binutils which already had that option before lib tool added it. so I guess if you have

anything you bake using bitbake is a recipe (input rules) which then generates packages (output) and there can be many packages generated from single recipes and one of the name of output package can

From Jeff's description, it sounded like the package (especially 'package version') comes from the stuff that is the recipe's *input*, and not the recipe's output -- if you've selected to build

I tried, according to the documentation at http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#extracting-the-root-filesystem), to configure and compile the autotooled GNU Hello World

The download site http://downloads.yoctoproject.org/releases/eclipse-plugin/1.2.1/indigo/ for the Eclipse plugin is not a correctly setup Eclipse download site. The site root does not have the correct

from here: http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#usingpoky-extend-customimage-custombb a couple gripes. end of 4.2.1 suggests IMAGE_INSTALL += "strace" when

Hi, How about these classes by the Linux

there really should be an official glossary somewhere, and it should be backed up with *actual* *examples* from the source as much as possible. that is, don't use "foo" if there's an existing

<bruce.ashfield@...> wrote: yes looking at 3.4 code. But havent tried that yet

The change would be to a core component, which is part of OE and which yocto pulls in — bitbake. So it would make no sense to send the patch here. No changes to bitbake are going into poky without

Do the OE people accept this wording too, or is this a yocto-project-only thing? In other words, should a potential patch be sent to OE or here?

It could, and should, be changed in that way, yes. -- Christopher Larson

Looks good to me. I'll queue it here with a few other fixes and do a test build against my existing binutils. I haven't looked yet, will 3.4+ need the same fix ? Cheers, Bruce

Hi Jeff, Thanks for your tasty metaphors! But your wording would seem to imply _a_ recipe builds _a_ package. But a recipe doesn't build a package, a recipe potentially builds lots of packages. For

Hi Tim - this sounds quite correct to me, and a good way to represent the process. Further, the elinux.org wiki page is coming along very well, and I would encourage you to add this to the page. I'd

There was an unintended power interruption during UPS electrical work at the OSU Open Source Lab today. Power to the Yocto Project racks was not impacted but the core router was briefly offline. This