yocto@lists.yoctoproject.org

Re: yocto tools on a nokia n800

Hello again! I think nokia n8xx could be a nice example of what yocto/poky are capable of. Especially now that Nokia has abandoned this devices, it would be cool to have a new OS being supported on

By tiagoprn <tiagoprn@...> · #172 ·

Re: Build failures on yocto

I'd just appreciate people being a little clearer about what they're attempting to do. Obviously I don't know how you've setup this balloon3 target but knowing this isn't an out the box

By Richard Purdie <rpurdie@...> · #171 ·

Re: Build failures on yocto

Hello, 2010/11/2 Richard Purdie <rpurdie@...>: Yes and yes. I'll attempt "atom-pc" later on, but that is not much of interest for me. Thanks. Best regards, -- Héctor Orón "Our Sun

By Hector Oron <hector.oron@...> · #170 ·

Re: Build failures on yocto

So to be clear, you set MACHINE="balloon3"? You're therefore building with some layer or additional metadata? I'd suggest trying a supported machine like "atom-pc" first before trying to add your

By Richard Purdie <rpurdie@...> · #169 ·

Re: Build failures on yocto

Only certainly variables can be passed through the environment. Can you put the line in local.conf please and retry as otherwise it won't have any effect. Ok, good. Cheers, Richard

By Richard Purdie <rpurdie@...> · #168 ·

Re: Build failures on yocto

Hello, 2010/11/2 Richard Purdie <rpurdie@...>: It is a balloon3 [1]. I think you have not official support for it. I also got an Intel Embedded Devkit 1-N450 (Black Sand) which I

By Hector Oron <hector.oron@...> · #167 ·

Re: Build failures on yocto

Hello, 2010/11/1 Richard Purdie <rpurdie@...>: Yes, it is 64 bit kernel host running a 32 bit userland. Linux enorme 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64

By Hector Oron <hector.oron@...> · #166 ·

Re: Build failures on yocto

Which MACHINE is that set for? Its unusual for the system to be using linux-dummy. Cheers, Richard

By Richard Purdie <rpurdie@...> · #165 ·

Re: Build failures on yocto

Hi, 2010/11/1 Hector Oron <hector.oron@...>: NOTE: package libtool-cross-2.2.10-r1: task do_package_write: Succeeded NOTE: Running task 1448 of 1529 (ID:

By Hector Oron <hector.oron@...> · #164 ·

Re: nightly-release takes more than 24 hours to build.

In case you didn't note Qing's investigation last week, attach his mail for your reference. Thanks Kevin

By Tian, Kevin <kevin.tian@...> · #162 ·

Poky weekly bug trend charts -- WW44

Hi all, This is the Poky weekly bug trend charts for last week (WW44). The open bug number increased to 133. There were only few bugs submitted/fixed in last week. The 1st chart indicates the total

By Xu, Jiajun <jiajun.xu@...> · #163 ·

Re: Bugzilla Changes

Agree in principle. Let me confirm: - kernel runtime (this includes all errors, panics, BUGs, etc. from the three categories I listed above - no objection). It's still 3 categories, but separate

By Darren Hart <dvhart@...> · #161 ·

Re: Bugzilla Changes

This is too much separation, having over categorization of the kernel defects at this point is overkill. I'd suggest three categories: - kernel build (which often transitions to straight up

By Bruce Ashfield <bruce.ashfield@...> · #160 ·

Re: Build failures on yocto

Hi, I don't have answers to all of the failures but let me try and respond to the ones I have some ideas about: At a guess this is a 64 bit kernel and a 32 bit userspace? What does "uname -a"

By Richard Purdie <rpurdie@...> · #159 ·

Re: Bugzilla Changes

Add Configurations - for the config/site data Remember this is not a Distribution, I think Yocto (Poky?) Meta-Data / Recipes and then the following components Add: User Space Recipes (this could

By Saul Wold <sgw@...> · #158 ·

Re: Bugzilla Changes

Good point. (See my reply to Mark's email) I think my lines might have run together! It was meant to be separate, and this looks like a good break down. Sau!

By Saul Wold <sgw@...> · #157 ·

Re: Bugzilla Changes

We'll also want to update this document after we make these changes: https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking We might want to streamline that doc a bit to better

By Foster, Dawn M <dawn.m.foster@...> · #156 ·

Re: Bugzilla Changes

I think this is where the Bugzilla description needs to be verbose. Toolchain for me includes: userspace kernel headers (but not the kernel), binutils, gcc, "the libc" (uclibc, glibc, eglibc), and

By Mark Hatle <mark.hatle@...> · #155 ·

Re: Bugzilla Changes

The divide between User Space and Tool Chain is a bit vague. For instance, I would generally expect to see glibc under User Space, but your description seems to place it under Tool Chain. Please keep

By Darren Hart <dvhart@...> · #154 ·

Re: Bugzilla Changes

My proposal -- similar bug slightly different: Poky Build System Bitbake Documentation General Poky Distribution Runtime Distribution -- Poky embedded linux distribution Documentation

By Mark Hatle <mark.hatle@...> · #153 ·

Messages