Date   

many "pkgconfig is needed" errors when building core-image-sato-dev for beagle

Robert P. J. Day
 

i'm sure there's a simple solution for this but i'm building
core-image-sato-dev for the beagleboard on my 64-bit ubuntu system
and the build eventually fails with *numerous* errors of the form:

Processing ...something...-dev:
error: Failed dependencies:
pkgconfig is needed ...
pkgconfig is needed ...
... etc etc ...

there are *pages* of that type of output for multiple tasks (the build
of core-image-sato worked fine).

i suspect the solution is something along the lines of this patch by
tom zanussi:

http://comments.gmane.org/gmane.linux.embedded.yocto.general/2716

but i'm not sure where to make the change. suggestions?

rday


--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Minutes: Yocto Technical Team Meeting - Tuesday, November 01, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada)

Liu, Song <song.liu@...>
 

Attendees:
Beth, Jessica, Tom, Matthew, Joshua, Mark, Jeff, Bruce, Richard, Saul, Darren, Song
 
Agenda:
 
Action items:
1. Song will work with Jiajun to get the QA plan ready for point releases.
2. Matthew will send out patch recommendations for Yocto 1.1.1 to the mailing list.
3. Saul will work with the team to complete the planning for the meta core team.
4. Richard will review unsorted features and prioritize them.
5. Song will change 1.2 schedule and extend M1, M3, M4 by one week due to no ELC in April next year.
6. Song to work with Shanghai team to break epic features into smaller ones.
 
 
* Opens collection - 5 min (Song)
* Yocto 1.0.2 and 1.1.1 point release update - 5 min (Josh)
- Haven't been any change since last time we check (2 weeks ago).
- 1.0.2: target Mid Nov. , Bruce will get kernel update by the end of this week. Song will talk to Jiajun to have the QA take to Jiajun on the testing. Still on Track.
- 1.1.1: Target the end of Nov to early Dec. Matthew has some patches, will put on the mailing lists. Start pulling things into the branch (Edison branch).
* Yocto 1.2 planning and M1 planning - 20 min (team)
- Feature planning for some features still need to be completed
- unsorted features need to be reviewed
- For those who have completed planning, please go ahead with the design process and development.
- Kernel team has done a great job for the planning.
- The design process: developers initiate, talk to various stakeholders, features need to be signed off by team leads and architect/Richard. Design process checklist.
- Status needs to be updated by feature owners every Monday on the white board after priority and estimate.
- Estimate: purpose, how we are going to use it: individual can use it for your milestone planning. But won't be used by overall planning or to calculate everyone's workload. After a couple of milestones, estimation will get better and will be used for next milestone planning, but will be adjusted all the time along the way, feel free to update any time. Another use of estimation is to find our epic features. Epic features need to be divided into smaller ones. Suggest to be less than 10 PD.
- Epic features need to be divided into smaller ones (< 10 PD), before scheduling it for milestones.
- Focus on a couple of features at a time until it's in master.
- Stabilization weeks: 'allow' time to fix bugs. But if you don't have any, please continue with features development. Priority during these weeks is to resolve build failures and bug fixing.
- Don't put off bug fixing during development weeks.
- Release boundary: We will release in April and October every year. The exact date of a release will vary depending on each release's circumstances.
 
* Opens - 10 min
- Open bug count (RP): The # bug is going up, people should pay attention and get more bugs fixed is possible.
 
* Weekly team sharing (20 min)
- Darren: Good reception in ELCE, RT workshop, lots of interests. Lot more interest of how to use the project than what the project is, we are making progress.
- Saul: Came back from ELC, working on planning with the team. No blocker.
- Richard: ELCE last week, trying to fix ongoing breakage. Catch up with bug patches. Email access has problem due to Linux Foundation network change. Remind me if there is anything I have not responded.
- Bruce: Sick last week, working on point release update, working on the 1.2 features.
- Jeff: vacation last week.
- Mark: investigation with x32 stuff, there is no prelink. Re-syncing to be upstream cause some problem. Two different issues on psudo. ETC for the fixes of these by the end of this week.
- Matthew: Nothing this time
- Tom: Working on meta-intel. Working through some packages, building issues, etc. review some documentation. ECG support.
- Jessica: ELC last week, sync with people on Linux tools, people show strong support of what we are doing. Sync up with 1.2 planning this week.
- Beth: last week 1.2 planning, some documentation work, fixing a build statistic bug, fix by the end of week.


Minutes: Yocto Technical Team Meeting - Tuesday, November 01, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada)

Liu, Song <song.liu@...>
 

Attendees:
Beth, Jessica, Tom, Matthew, Joshua, Mark, Jeff, Bruce, Richard, Saul, Darren, Song
 
Agenda:
 
Action items:
1. Song will work with Jiajun to get the QA plan ready for point releases.
2. Matthew will send out patch recommendations for Yocto 1.1.1 to the mailing list.
3. Saul will work with the team to complete the planning for the meta core team.
4. Richard will review unsorted features and prioritize them.
5. Song will change 1.2 schedule and extend M1, M3, M4 by one week due to no ELC in April next year.
6. Song to work with Shanghai team to break epic features into smaller ones.
 
 
* Opens collection - 5 min (Song)
* Yocto 1.0.2 and 1.1.1 point release update - 5 min (Josh)
- Haven't been any change since last time we check (2 weeks ago).
- 1.0.2: target Mid Nov. , Bruce will get kernel update by the end of this week. Song will talk to Jiajun to have the QA take to Jiajun on the testing. Still on Track.
- 1.1.1: Target the end of Nov to early Dec. Matthew has some patches, will put on the mailing lists. Start pulling things into the branch (Edison branch).
* Yocto 1.2 planning and M1 planning - 20 min (team)
- Feature planning for some features still need to be completed
- unsorted features need to be reviewed
- For those who have completed planning, please go ahead with the design process and development.
- Kernel team has done a great job for the planning.
- The design process: developers initiate, talk to various stakeholders, features need to be signed off by team leads and architect/Richard. Design process checklist.
- Status needs to be updated by feature owners every Monday on the white board after priority and estimate.
- Estimate: purpose, how we are going to use it: individual can use it for your milestone planning. But won't be used by overall planning or to calculate everyone's workload. After a couple of milestones, estimation will get better and will be used for next milestone planning, but will be adjusted all the time along the way, feel free to update any time. Another use of estimation is to find our epic features. Epic features need to be divided into smaller ones. Suggest to be less than 10 PD.
- Epic features need to be divided into smaller ones (< 10 PD), before scheduling it for milestones.
- Focus on a couple of features at a time until it's in master.
- Stabilization weeks: 'allow' time to fix bugs. But if you don't have any, please continue with features development. Priority during these weeks is to resolve build failures and bug fixing.
- Don't put off bug fixing during development weeks.
- Release boundary: We will release in April and October every year. The exact date of a release will vary depending on each release's circumstances.
 
* Opens - 10 min
- Open bug count (RP): The # bug is going up, people should pay attention and get more bugs fixed is possible.
 
* Weekly team sharing (20 min)
- Darren: Good reception in ELCE, RT workshop, lots of interests. Lot more interest of how to use the project than what the project is, we are making progress.
- Saul: Came back from ELC, working on planning with the team. No blocker.
- Richard: ELCE last week, trying to fix ongoing breakage. Catch up with bug patches. Email access has problem due to Linux Foundation network change. Remind me if there is anything I have not responded.
- Bruce: Sick last week, working on point release update, working on the 1.2 features.
- Jeff: vacation last week.
- Mark: investigation with x32 stuff, there is no prelink. Re-syncing to be upstream cause some problem. Two different issues on psudo. ETC for the fixes of these by the end of this week.
- Matthew: Nothing this time
- Tom: Working on meta-intel. Working through some packages, building issues, etc. review some documentation. ECG support.
- Jessica: ELC last week, sync with people on Linux tools, people show strong support of what we are doing. Sync up with 1.2 planning this week.
- Beth: last week 1.2 planning, some documentation work, fixing a build statistic bug, fix by the end of week.


list of images in appendix D of poky ref manual seems incomplete

Robert P. J. Day
 

just noticed that Appendix D of the poky reference manual lists the
supported images, and suggests you can see them all with:

$ ls meta*/recipes*/images/*.bb

but the list in that appendix doesn't mention the following:

meta/recipes-qt/images/qt4e-demo-image.bb
meta/recipes-rt/images/core-image-rt.bb
meta/recipes-rt/images/core-image-rt-sdk.bb

should it?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


digest mail replies, was Re: yocto Digest, Vol 13, Issue 54

Koen Kooi
 

Op 31 okt. 2011, om 19:42 heeft Mike Tsukerman het volgende geschreven:



On Mon, Oct 31, 2011 at 10:29 PM, <yocto-request@...> wrote:
[..]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of yocto digest..."

Please pay attention to the above!


Re: Slow-startup.

Adrian Alonso <aalonso00@...>
 

Hi Noel,

Are you also integrating Freescale xorg driver and related libs?
Also Freescale has a large set of patchs for the kernel that are not
in mainstream, you can take a look at L2.6.35_11.09.01_ER_source_boundle.tar.gz
located at [1] and [2] which is an experimental meta layer than I'm working on for adding
Freescale Arm support but still has some problems thanks to the way Fsl distributes it's
source code and need to manually copy some source packages in Pokys download dir;


On Thu, Oct 27, 2011 at 11:10 AM, Vellemans, Noel <Noel.Vellemans@...> wrote:

Hi all,

I'm test-driving the yocto-edison version, Target-armv7 (testing on imx-53x cpu).

But,  I’m having a strange problem.

It takes very long to start the device, every time [not only the first time], at each reboot cycle it takes up to 3 minutes before I get the desktop.

At the current time I got to the point (by using printf into the code on 1001 places)  that it is the _mb_font_load() in matchbox-lib that makes the startup extremely slow. (system seems to ‘hang’ for more the 3 minutes before the matchbox-desktop pops up.)


Any information available on this?
Any hints where to look at ?


Kind regards
Noel


_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto




--
Saludos
Adrian Alonso
http://aalonso.wordpress.com


Agenda: Yocto Technical Team Meeting - Tuesday, November 01, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada)

Liu, Song <song.liu@...>
 

* Opens collection - 5 min (Song)
* Yocto 1.0.2 and 1.1.1 point release update - 5 min (Josh)
* Yocto 1.2 planning and M1 planning - 20 min (team)
https://wiki.yoctoproject.org/wiki/Yocto_1.2_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_1.2_Features
* Opens - 10 min
* Weekly team sharing (20 min)


-----Original Appointment-----
From: Liu, Song
Sent: Tuesday, August 16, 2011 3:27 PM
To: 'McCombe, Kevin'; Wold, Saul; Zhang, Jessica; 'deVries, Alex'; 'Polk, Jeffrey'; 'Hatle, Mark'; Purdie, Richard; Li, Susie; Lock, Joshua; 'Bruce Ashfield'; Zanussi, Tom; Hart, Darren; Flanagan, Elizabeth; Stewart, David C; 'Lieu.Ta@...'; 'paul.anderson@...'; Osier-mixon, Jeffrey; Dmytriyenko, Denys; Kooi, Koen; 'yocto-ab@...'; Erway, Tracey M; 'Daniel Cauchy'; Wang, Shane; 'Kridner, Jason'; Yu, Ke; Rifenbark, Scott M; 'Dixon, Brad'; 'Jeremy Puhlman'; yocto@...; 'shsift-yocto@...'
Cc: 'morvek@...'; 'Ruff, Nithya'; Moeller, Thorsten; Saxena, Rahul; 'Ranslam, Rob'; 'Anders Darander'; Bodke, Kishore K
Subject: Yocto Technical Team Meeting
When: Tuesday, November 01, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Bridge Info Enclosed



Conference details
Conference name:
Yocto Technical Team
Conference date/start time:
Tue Jun 28, 2011 at 10:00 AM Central Daylight Time
Participants:
30
Duration:
60 minutes
Participant passcode:
49611427
Dial-in number:
1.972.995.7777
US Toll Free number:
1.877.561.6828
BlackBerry users, click this link to join your conference as a chairperson:
1.972.995.7777x67184230#
BlackBerry users, click this link to join your conference as a participant:
1.972.995.7777x49611427#
 
Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.

Local and Global Access Numbers


Country
Dial-in number
Australia:
1800 636 843
Czech Republic:
242 430 350
China (Beijing):
From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai):
From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen):
From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities):
From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark:
8060 1400
Finland:
09 41333477
France:
0497 275888
Germany:
08161 803232
Holland:
030 2417490
India:
BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel:
09 790 6715
Italy:
039 69061234 (039 is local city code not country code)
Japan:
From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia:
From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway:
2 295 8744
Philippines:
From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore:
From IP phone dial 3894777
Outside TI use 6389 4777
South Korea:
From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden:
08 58755577
Taiwan:
From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey:
Landline Only dial 0811 288 0001
then enter 877 633 1123
UK:
01604 663003
US:
972 995 7777 or 1877 561 6828

Recurring conferences
First scheduled conference:
Tue Jun 28, 2011
Recurrence frequency:
Weekly - Every 1 week(s) on Tuesday
Recurrence ends:
End on Fri Jun 22, 2012, 10:40 AM CDT


Re: Which filesystem for target?

Chris Tapp
 

On 31 Oct 2011, at 10:16, Paul Eggleton wrote:

On Friday 28 October 2011 23:11:22 Chris Tapp wrote:
Which is the 'best' filesystem to use for an embedded device that's
using a CF card?

...
Arnd Bergmann gave a talk at ELCE on flash drive performance (something he has
done quite a lot of research on); I did not attend but Darren and I spoke to
him later on, and if I recall correctly in his tests btrfs performed the best.
Hopefully the talk video will be available soon thanks to the folks at Free
Electrons; in the mean time there's an earlier article by Arnd on this topic
here:

http://lwn.net/Articles/428584/
Thanks, that's a very good article that may explain some issues I've been seeing.

Chris


Re: yocto Digest, Vol 13, Issue 54

Mike Tsukerman <miketsukerman@...>
 



On Mon, Oct 31, 2011 at 10:29 PM, <yocto-request@...> wrote:
Send yocto mailing list submissions to
       yocto@...

To subscribe or unsubscribe via the World Wide Web, visit
       https://lists.yoctoproject.org/listinfo/yocto
or, via email, send a message with subject or body 'help' to
       yocto-request@...

You can reach the person managing the list at
       yocto-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of yocto digest..."


Today's Topics:

  1. Re: any objection to adding a PREMIRRORS section to the QS
     guide? (Robert P. J. Day)
  2. Re: root paths in packages (McClintock Matthew-B29882)
  3. Re: [PATCH 1/2] meta-romley: Fix BSP description in
     romley.conf (Bodke, Kishore K)
  4. Re: [PATCH 2/2] meta-romley: change references to sugarbay in
     linux-yocto-rt_3.0.bbappend (Bodke, Kishore K)
  5. Re: root paths in packages (Mark Hatle)
  6. Re: what's the proper value for BB_NUMBER_THREADS? (Mark Hatle)
  7. Re: what's the proper value for BB_NUMBER_THREADS?
     (Robert P. J. Day)
  8. Re: what's the proper value for BB_NUMBER_THREADS? (Gary Thomas)
  9. Re: root paths in packages (McClintock Matthew-B29882)


----------------------------------------------------------------------

Message: 1
Date: Mon, 31 Oct 2011 12:01:26 -0400 (EDT)
From: "Robert P. J. Day" <rpjday@...>
To: "Rifenbark, Scott M" <scott.m.rifenbark@...>
Cc: Yocto discussion list <yocto@...>
Subject: Re: [yocto] any objection to adding a PREMIRRORS section to
       the QS guide?
Message-ID:
       <alpine.DEB.2.02.1110311150440.7448@...>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 31 Oct 2011, Rifenbark, Scott M wrote:

> Robert,
>
> We do have a question addressed in the Yocto Project Reference
> Manual that talks about premirrors and how Poky finds stuff.  See
> the H.24 section of the manual
> http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html.
> Maybe this information is a bit too buried to be useful.  I could
> specifically reference that FAQ entry from within the QS in the same
> area that I mention the other "useful" items to consider in the
> local.conf file, such as BB_NUMBER_THREADS, etc.
>
> Scott

 i know about the PREMIRRORS stuff in the poky reference manual -- i
was just toying with the idea that knowing how PREMIRRORS works would
be useful, even for a beginner.

 perhaps i'm not using it properly, but in my case, it's handy since
i have a downloads directory of nothing but tarballs that i've been
accumulating over the last while that i've used for openembedded and
other projects. i'm using PREMIRRORS_prepend to take advantage of all
that content to avoid any unnecessary downloading.  and every time i
*do* end up downloading a newer version of a tarball that i didn't
have, i copy it to that central downloads directory for the next time.
does that make sense?  and, as i said, even beginners should be able
to appreciate taking advantage of local content they may have
collected for other reasons.

 in any event, i have some different ideas for the design of a
beginner's guide i plan on using in some of my own presentations, so i
don't have to inflict all of my ideas on everyone else.

rday

--

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                       http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


------------------------------

Message: 2
Date: Mon, 31 Oct 2011 16:32:23 +0000
From: McClintock Matthew-B29882 <B29882@...>
To: Mike Tsukerman <miketsukerman@...>
Cc: "yocto@..." <yocto@...>
Subject: Re: [yocto] root paths in packages
Message-ID:
       <CAEsOVNd18cWS5JeaxHMLTR9-pr+65bb4s=qc7H_6Prq1PpTzbw@...>
Content-Type: text/plain; charset="iso-8859-1"

On Mon, Oct 31, 2011 at 5:57 AM, Mike Tsukerman <miketsukerman@...> wrote:
> Hello,
> I've build rpm packages and met some interesting things.
> In the rpm all scripts and files include root paths from machine that i've
> build on.
> how can i change that?

Which package? Can you give some examples?

-M

- Hide quoted text -
On Mon, Oct 31, 2011 at 10:26 PM, McClintock Matthew-B29882 <B29882@...> wrote:
On Mon, Oct 31, 2011 at 11:40 AM, Mike Tsukerman
<miketsukerman@...> wrote:
   What commands did you run to generate this rpm? What file is this in?
Usually the shebang should be updated to remove any references to
build environment but it looks like it's still referencing perl-native
from the build environment.

Is this script used on the target machine or just during the build
process? It might not be explicitly required.

 
I've run MACHINE=beagleboard bitbake world. Then i get a lot of rpms in armv7a-vfp-neon folder. 
I have an igep0020 board, and core-image-minimal-dev running on it. I use these rpm's on the board.
And as expected dpkg is not working before i found that it includes these paths.
But all other rpm's have the same problems - in INSTALL and UPGRADE scripts i've found root paths.  

rpm --nosignature -ivh /media/mdev/yocto/poky/build/tmp/deploy/rpm/armv7a-vfp-neon/zip-dev-3.0-r0.armv7a.rpm

 

------------------------------

Message: 3
Date: Mon, 31 Oct 2011 10:01:06 -0700
From: "Bodke, Kishore K" <kishore.k.bodke@...>
To: "Zanussi, Tom" <tom.zanussi@...>, "yocto@..."
       <yocto@...>
Subject: Re: [yocto] [PATCH 1/2] meta-romley: Fix BSP description in
       romley.conf
Message-ID:
       <4BD43A85686FC34D819098DB1C3999D9018F70901D@...>

Content-Type: text/plain; charset="us-ascii"

Acked-by: Kishore Bodke  <Kishore.k.bodke@...>

Thanks
Kishore.

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of tom.zanussi@...
Sent: Friday, October 28, 2011 7:00 AM
To: yocto@...
Subject: [yocto] [PATCH 1/2] meta-romley: Fix BSP description in romley.conf

From: Tom Zanussi <tom.zanussi@...>

The description still had a reference to Sugar Bay; this changes it to
Romley.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
 meta-romley/conf/machine/romley.conf |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-romley/conf/machine/romley.conf b/meta-romley/conf/machine/romley.conf
index 38bd17a..2dcb5db 100644
--- a/meta-romley/conf/machine/romley.conf
+++ b/meta-romley/conf/machine/romley.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
 #@NAME: romley

-#@DESCRIPTION: Machine configuration for Sugar Bay systems
+#@DESCRIPTION: Machine configuration for Romley systems
 # i.e. Sandy Bridge + Patsburg Chipset

 require conf/machine/include/tune-x86_64.inc
--
1.7.0.4

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


------------------------------

Message: 4
Date: Mon, 31 Oct 2011 10:03:47 -0700
From: "Bodke, Kishore K" <kishore.k.bodke@...>
To: "Zanussi, Tom" <tom.zanussi@...>, "yocto@..."
       <yocto@...>
Subject: Re: [yocto] [PATCH 2/2] meta-romley: change references to
       sugarbay in     linux-yocto-rt_3.0.bbappend
Message-ID:
       <4BD43A85686FC34D819098DB1C3999D9018F709021@...>

Content-Type: text/plain; charset="us-ascii"

Acked-by: Kishore Bodke  <Kishore.k.bodke@...>

Thanks
Kishore.

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of tom.zanussi@...
Sent: Friday, October 28, 2011 7:00 AM
To: yocto@...
Subject: [yocto] [PATCH 2/2] meta-romley: change references to sugarbay in linux-yocto-rt_3.0.bbappend

From: Tom Zanussi <tom.zanussi@...>

There are still references to sugarbay in linux-yocto-rt_3.0.bbappend;
this changes them to romley.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
 .../linux/linux-yocto-rt_3.0.bbappend              |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
index d630dc4..1551ccf 100644
--- a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
+++ b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
@@ -3,6 +3,6 @@ COMPATIBLE_MACHINE_romley = "romley"
 KMACHINE_romley  = "romley"

 # Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_sugarbay  = "yocto/standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_sugarbay ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_sugarbay ?= XXXX
+#KBRANCH_romley  = "yocto/standard/preempt-rt/base"
+#SRCREV_machine_pn-linux-yocto-rt_romley ?= XXXX
+#SRCREV_meta_pn-linux-yocto-rt_romley ?= XXXX
--
1.7.0.4

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


------------------------------

Message: 5
Date: Mon, 31 Oct 2011 12:12:08 -0500
From: Mark Hatle <mark.hatle@...>
To: <yocto@...>
Subject: Re: [yocto] root paths in packages
Message-ID: <4EAED6E8.3080800@...>
Content-Type: text/plain; charset="ISO-8859-1"

On 10/31/11 5:57 AM, Mike Tsukerman wrote:
> Hello,
>
> I've build rpm packages and met some interesting things.
> In the rpm all scripts and files include root paths from machine that i've build on.
> how can i change that?

Examples of the problem are definitely needed.  There are some cases where
embedded paths simply refer to the place on the disk a source file or similar
came from during the build.  Depending on where these references are, they may
be considered safe and acceptable.  However, in most places something like this
would be considered an error.

--Mark

> --
> Best regards, Mike Tsukerman
>
> jabber: miketsukerman@... <mailto:miketsukerman@...>
> jabber: warzon@... <mailto:warzon@...>
> skype: w_a_r_z_o_n
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@...
> https://lists.yoctoproject.org/listinfo/yocto



------------------------------

Message: 6
Date: Mon, 31 Oct 2011 12:15:28 -0500
From: Mark Hatle <mark.hatle@...>
To: <yocto@...>
Subject: Re: [yocto] what's the proper value for BB_NUMBER_THREADS?
Message-ID: <4EAED7B0.4050909@...>
Content-Type: text/plain; charset="ISO-8859-1"

On 10/30/11 11:15 AM, Robert P. J. Day wrote:
> On Sun, 30 Oct 2011, Christian Gagneraud wrote:
>
>> On 30/10/11 15:32, Robert P. J. Day wrote:
>>>
>>>    all the docs recommend twice the number of cores (AFAICT), yet the
>>> template local.conf file suggests that, for a quad core, the value of
>>> 4 would be appropriate.  shouldn't that say 8?  same with
>>> PARALLEL_MAKE?
>>
>> Hi Robert,
>>
>> The Poky ref manual says (rule of thumb) x2 for BB_NUMBER_THREADS,
>> and x1.5 for PARALLEL_MAKE.
>
>   if that's the case, anyone object to my submitting a patch to
> update local.conf.sample appropriately?
>
> rday
>

I agree the manual and local.conf files should match.  The issue seems to be
that the perfect values are subjective.  Things like memory, disk speed, chipset
latency, and of course processor speed/cores all affect the optimal setting.
But we do need a consistent rule of thumb..  I myself usually use x2 for both
THREADS and MAKE.

--Mark


------------------------------

Message: 7
Date: Mon, 31 Oct 2011 13:25:03 -0400 (EDT)
From: "Robert P. J. Day" <rpjday@...>
To: Mark Hatle <mark.hatle@...>
Cc: yocto@...
Subject: Re: [yocto] what's the proper value for BB_NUMBER_THREADS?
Message-ID:
       <alpine.DEB.2.02.1110311323050.8545@...>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 31 Oct 2011, Mark Hatle wrote:

> On 10/30/11 11:15 AM, Robert P. J. Day wrote:
> > On Sun, 30 Oct 2011, Christian Gagneraud wrote:
> >
> >> On 30/10/11 15:32, Robert P. J. Day wrote:
> >>>
> >>>    all the docs recommend twice the number of cores (AFAICT), yet the
> >>> template local.conf file suggests that, for a quad core, the value of
> >>> 4 would be appropriate.  shouldn't that say 8?  same with
> >>> PARALLEL_MAKE?
> >>
> >> Hi Robert,
> >>
> >> The Poky ref manual says (rule of thumb) x2 for BB_NUMBER_THREADS,
> >> and x1.5 for PARALLEL_MAKE.
> >
> >   if that's the case, anyone object to my submitting a patch to
> > update local.conf.sample appropriately?
> >
> > rday
> >
>
> I agree the manual and local.conf files should match.  The issue
> seems to be that the perfect values are subjective.  Things like
> memory, disk speed, chipset latency, and of course processor
> speed/cores all affect the optimal setting. But we do need a
> consistent rule of thumb..  I myself usually use x2 for both THREADS
> and MAKE.

 that's what i would normally use, assuming that having an overly
high value for either of those settings can't possibly hurt.  if
that's the consensus, i can adjust the references to say 2x everywhere
that i know of.  just let me know.

rday

--

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                       http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


------------------------------

Message: 8
Date: Mon, 31 Oct 2011 11:39:06 -0600
From: Gary Thomas <gary@...>
To: "Robert P. J. Day" <rpjday@...>
Cc: yocto@...
Subject: Re: [yocto] what's the proper value for BB_NUMBER_THREADS?
Message-ID: <4EAEDD3A.9070601@...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 2011-10-31 11:25, Robert P. J. Day wrote:
> On Mon, 31 Oct 2011, Mark Hatle wrote:
>
>> On 10/30/11 11:15 AM, Robert P. J. Day wrote:
>>> On Sun, 30 Oct 2011, Christian Gagneraud wrote:
>>>
>>>> On 30/10/11 15:32, Robert P. J. Day wrote:
>>>>>
>>>>>     all the docs recommend twice the number of cores (AFAICT), yet the
>>>>> template local.conf file suggests that, for a quad core, the value of
>>>>> 4 would be appropriate.  shouldn't that say 8?  same with
>>>>> PARALLEL_MAKE?
>>>>
>>>> Hi Robert,
>>>>
>>>> The Poky ref manual says (rule of thumb) x2 for BB_NUMBER_THREADS,
>>>> and x1.5 for PARALLEL_MAKE.
>>>
>>>    if that's the case, anyone object to my submitting a patch to
>>> update local.conf.sample appropriately?
>>>
>>> rday
>>>
>>
>> I agree the manual and local.conf files should match.  The issue
>> seems to be that the perfect values are subjective.  Things like
>> memory, disk speed, chipset latency, and of course processor
>> speed/cores all affect the optimal setting. But we do need a
>> consistent rule of thumb..  I myself usually use x2 for both THREADS
>> and MAKE.
>
>    that's what i would normally use, assuming that having an overly
> high value for either of those settings can't possibly hurt.  if
> that's the consensus, i can adjust the references to say 2x everywhere
> that i know of.  just let me know.

Look back in the archives - I think it was Richard that did a fairly
extensive study of this and he (whoever it was) found that there were
saturation points and trying to get beyond them had a negative impact.

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


------------------------------

Message: 9
Date: Mon, 31 Oct 2011 18:27:27 +0000
From: McClintock Matthew-B29882 <B29882@...>
To: Mike Tsukerman <miketsukerman@...>
Cc: "yocto@..." <yocto@...>
Subject: Re: [yocto] root paths in packages
Message-ID:
       <CAEsOVNeP_tPvsB0BEX2tLXK=sEHP1=NSSEPEX4GVwMiAwr2-_Q@...>
Content-Type: text/plain; charset="iso-8859-1"

On Mon, Oct 31, 2011 at 11:40 AM, Mike Tsukerman
<miketsukerman@...> wrote:
> I'am using upstream release from git repository.
> my building path is /media/mdev/yocto/poky/build/.
> For example dpkg rpm package for armv7 neon. But it's the same for ?all
> other packages. This cause many many errors and faults.
> i've attached to the letter screenshot with example.
> On Mon, Oct 31, 2011 at 8:32 PM, McClintock Matthew-B29882
> <B29882@...> wrote:
>>
>> On Mon, Oct 31, 2011 at 5:57 AM, Mike Tsukerman <miketsukerman@...>
>> wrote:
>> > Hello,
>> > I've build rpm packages and met some interesting things.
>> > In the rpm all scripts and files include root paths from machine that
>> > i've
>> > build on.
>> > how can i change that?

Mike,

You need to reply all to include the mailing list.

What commands did you run to generate this rpm? What file is this in?
Usually the shebang should be updated to remove any references to
build environment but it looks like it's still referencing perl-native
from the build environment.

Is this script used on the target machine or just during the build
process? It might not be explicitly required.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example.png
Type: image/png
Size: 162063 bytes
Desc: example.png
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20111031/af29d2b9/attachment.png>

------------------------------

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


End of yocto Digest, Vol 13, Issue 54
*************************************



--
Best regards, Mike Tsukerman

jabber: miketsukerman@...
jabber: warzon@...
skype: w_a_r_z_o_n


Re: root paths in packages

McClintock Matthew-B29882 <B29882@...>
 

On Mon, Oct 31, 2011 at 11:40 AM, Mike Tsukerman
<miketsukerman@...> wrote:
I'am using upstream release from git repository.
my building path is /media/mdev/yocto/poky/build/.
For example dpkg rpm package for armv7 neon. But it's the same for  all
other packages. This cause many many errors and faults.
i've attached to the letter screenshot with example.
On Mon, Oct 31, 2011 at 8:32 PM, McClintock Matthew-B29882
<B29882@...> wrote:

On Mon, Oct 31, 2011 at 5:57 AM, Mike Tsukerman <miketsukerman@...>
wrote:
Hello,
I've build rpm packages and met some interesting things.
In the rpm all scripts and files include root paths from machine that
i've
build on.
how can i change that?
Mike,

You need to reply all to include the mailing list.

What commands did you run to generate this rpm? What file is this in?
Usually the shebang should be updated to remove any references to
build environment but it looks like it's still referencing perl-native
from the build environment.

Is this script used on the target machine or just during the build
process? It might not be explicitly required.


Re: what's the proper value for BB_NUMBER_THREADS?

Gary Thomas
 

On 2011-10-31 11:25, Robert P. J. Day wrote:
On Mon, 31 Oct 2011, Mark Hatle wrote:

On 10/30/11 11:15 AM, Robert P. J. Day wrote:
On Sun, 30 Oct 2011, Christian Gagneraud wrote:

On 30/10/11 15:32, Robert P. J. Day wrote:

all the docs recommend twice the number of cores (AFAICT), yet the
template local.conf file suggests that, for a quad core, the value of
4 would be appropriate. shouldn't that say 8? same with
PARALLEL_MAKE?
Hi Robert,

The Poky ref manual says (rule of thumb) x2 for BB_NUMBER_THREADS,
and x1.5 for PARALLEL_MAKE.
if that's the case, anyone object to my submitting a patch to
update local.conf.sample appropriately?

rday
I agree the manual and local.conf files should match. The issue
seems to be that the perfect values are subjective. Things like
memory, disk speed, chipset latency, and of course processor
speed/cores all affect the optimal setting. But we do need a
consistent rule of thumb.. I myself usually use x2 for both THREADS
and MAKE.
that's what i would normally use, assuming that having an overly
high value for either of those settings can't possibly hurt. if
that's the consensus, i can adjust the references to say 2x everywhere
that i know of. just let me know.
Look back in the archives - I think it was Richard that did a fairly
extensive study of this and he (whoever it was) found that there were
saturation points and trying to get beyond them had a negative impact.

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------


Re: what's the proper value for BB_NUMBER_THREADS?

Robert P. J. Day
 

On Mon, 31 Oct 2011, Mark Hatle wrote:

On 10/30/11 11:15 AM, Robert P. J. Day wrote:
On Sun, 30 Oct 2011, Christian Gagneraud wrote:

On 30/10/11 15:32, Robert P. J. Day wrote:

all the docs recommend twice the number of cores (AFAICT), yet the
template local.conf file suggests that, for a quad core, the value of
4 would be appropriate. shouldn't that say 8? same with
PARALLEL_MAKE?
Hi Robert,

The Poky ref manual says (rule of thumb) x2 for BB_NUMBER_THREADS,
and x1.5 for PARALLEL_MAKE.
if that's the case, anyone object to my submitting a patch to
update local.conf.sample appropriately?

rday
I agree the manual and local.conf files should match. The issue
seems to be that the perfect values are subjective. Things like
memory, disk speed, chipset latency, and of course processor
speed/cores all affect the optimal setting. But we do need a
consistent rule of thumb.. I myself usually use x2 for both THREADS
and MAKE.
that's what i would normally use, assuming that having an overly
high value for either of those settings can't possibly hurt. if
that's the consensus, i can adjust the references to say 2x everywhere
that i know of. just let me know.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Re: what's the proper value for BB_NUMBER_THREADS?

Mark Hatle <mark.hatle@...>
 

On 10/30/11 11:15 AM, Robert P. J. Day wrote:
On Sun, 30 Oct 2011, Christian Gagneraud wrote:

On 30/10/11 15:32, Robert P. J. Day wrote:

all the docs recommend twice the number of cores (AFAICT), yet the
template local.conf file suggests that, for a quad core, the value of
4 would be appropriate. shouldn't that say 8? same with
PARALLEL_MAKE?
Hi Robert,

The Poky ref manual says (rule of thumb) x2 for BB_NUMBER_THREADS,
and x1.5 for PARALLEL_MAKE.
if that's the case, anyone object to my submitting a patch to
update local.conf.sample appropriately?

rday
I agree the manual and local.conf files should match. The issue seems to be
that the perfect values are subjective. Things like memory, disk speed, chipset
latency, and of course processor speed/cores all affect the optimal setting.
But we do need a consistent rule of thumb.. I myself usually use x2 for both
THREADS and MAKE.

--Mark


Re: root paths in packages

Mark Hatle <mark.hatle@...>
 

On 10/31/11 5:57 AM, Mike Tsukerman wrote:
Hello,

I've build rpm packages and met some interesting things.
In the rpm all scripts and files include root paths from machine that i've build on.
how can i change that?
Examples of the problem are definitely needed. There are some cases where
embedded paths simply refer to the place on the disk a source file or similar
came from during the build. Depending on where these references are, they may
be considered safe and acceptable. However, in most places something like this
would be considered an error.

--Mark

--
Best regards, Mike Tsukerman

jabber: miketsukerman@... <mailto:miketsukerman@...>
jabber: warzon@... <mailto:warzon@...>
skype: w_a_r_z_o_n



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: [PATCH 2/2] meta-romley: change references to sugarbay in linux-yocto-rt_3.0.bbappend

Bodke, Kishore K <kishore.k.bodke@...>
 

Acked-by: Kishore Bodke <Kishore.k.bodke@...>

Thanks
Kishore.

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of tom.zanussi@...
Sent: Friday, October 28, 2011 7:00 AM
To: yocto@...
Subject: [yocto] [PATCH 2/2] meta-romley: change references to sugarbay in linux-yocto-rt_3.0.bbappend

From: Tom Zanussi <tom.zanussi@...>

There are still references to sugarbay in linux-yocto-rt_3.0.bbappend;
this changes them to romley.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
.../linux/linux-yocto-rt_3.0.bbappend | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
index d630dc4..1551ccf 100644
--- a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
+++ b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
@@ -3,6 +3,6 @@ COMPATIBLE_MACHINE_romley = "romley"
KMACHINE_romley = "romley"

# Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_sugarbay = "yocto/standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_sugarbay ?= XXXX
-#SRCREV_meta_pn-linux-yocto-rt_sugarbay ?= XXXX
+#KBRANCH_romley = "yocto/standard/preempt-rt/base"
+#SRCREV_machine_pn-linux-yocto-rt_romley ?= XXXX
+#SRCREV_meta_pn-linux-yocto-rt_romley ?= XXXX
--
1.7.0.4

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: [PATCH 1/2] meta-romley: Fix BSP description in romley.conf

Bodke, Kishore K <kishore.k.bodke@...>
 

Acked-by: Kishore Bodke <Kishore.k.bodke@...>

Thanks
Kishore.

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of tom.zanussi@...
Sent: Friday, October 28, 2011 7:00 AM
To: yocto@...
Subject: [yocto] [PATCH 1/2] meta-romley: Fix BSP description in romley.conf

From: Tom Zanussi <tom.zanussi@...>

The description still had a reference to Sugar Bay; this changes it to
Romley.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-romley/conf/machine/romley.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-romley/conf/machine/romley.conf b/meta-romley/conf/machine/romley.conf
index 38bd17a..2dcb5db 100644
--- a/meta-romley/conf/machine/romley.conf
+++ b/meta-romley/conf/machine/romley.conf
@@ -1,7 +1,7 @@
#@TYPE: Machine
#@NAME: romley

-#@DESCRIPTION: Machine configuration for Sugar Bay systems
+#@DESCRIPTION: Machine configuration for Romley systems
# i.e. Sandy Bridge + Patsburg Chipset

require conf/machine/include/tune-x86_64.inc
--
1.7.0.4

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: root paths in packages

McClintock Matthew-B29882 <B29882@...>
 

On Mon, Oct 31, 2011 at 5:57 AM, Mike Tsukerman <miketsukerman@...> wrote:
Hello,
I've build rpm packages and met some interesting things.
In the rpm all scripts and files include root paths from machine that i've
build on.
how can i change that?
Which package? Can you give some examples?

-M


Re: any objection to adding a PREMIRRORS section to the QS guide?

Robert P. J. Day
 

On Mon, 31 Oct 2011, Rifenbark, Scott M wrote:

Robert,

We do have a question addressed in the Yocto Project Reference
Manual that talks about premirrors and how Poky finds stuff. See
the H.24 section of the manual
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html.
Maybe this information is a bit too buried to be useful. I could
specifically reference that FAQ entry from within the QS in the same
area that I mention the other "useful" items to consider in the
local.conf file, such as BB_NUMBER_THREADS, etc.

Scott
i know about the PREMIRRORS stuff in the poky reference manual -- i
was just toying with the idea that knowing how PREMIRRORS works would
be useful, even for a beginner.

perhaps i'm not using it properly, but in my case, it's handy since
i have a downloads directory of nothing but tarballs that i've been
accumulating over the last while that i've used for openembedded and
other projects. i'm using PREMIRRORS_prepend to take advantage of all
that content to avoid any unnecessary downloading. and every time i
*do* end up downloading a newer version of a tarball that i didn't
have, i copy it to that central downloads directory for the next time.
does that make sense? and, as i said, even beginners should be able
to appreciate taking advantage of local content they may have
collected for other reasons.

in any event, i have some different ideas for the design of a
beginner's guide i plan on using in some of my own presentations, so i
don't have to inflict all of my ideas on everyone else.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Re: couple questions about cleaning up the Quick Start Guide

Robert P. J. Day
 

On Mon, 31 Oct 2011, Rifenbark, Scott M wrote:

Robert,

Thanks for the stuff and the look here. Regarding your first point
- I don't have a problem using the real link over the redirect.
The only things that come to mind are if they work why change them?
But, if the community wants the downloads.yoctoproject.org/releases
URL in there I can certainly go in and make changes to master.
yes, that's a judgment call, someone else can make that decision.
obviously, not a critical change.

On the second point - you are absolutely correct here. I will fix
that in master to reflect where the tarball really is. I think as
the project moves forward there will be more consistency. Early
life jitters I guess :)
i suspect you've already seen the two patches i posted yesterday.
just apply what you think is useful, i've already moved on to the next
manual i'm fighting with. :-)

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Re: any objection to adding a PREMIRRORS section to the QS guide?

Rifenbark, Scott M <scott.m.rifenbark@...>
 

Robert,

We do have a question addressed in the Yocto Project Reference Manual that talks about premirrors and how Poky finds stuff. See the H.24 section of the manual http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html. Maybe this information is a bit too buried to be useful. I could specifically reference that FAQ entry from within the QS in the same area that I mention the other "useful" items to consider in the local.conf file, such as BB_NUMBER_THREADS, etc.

Scott

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Robert P. J. Day
Sent: Sunday, October 30, 2011 7:40 AM
To: Yocto discussion list
Subject: [yocto] any objection to adding a PREMIRRORS section to the QS guide?


perhaps outside the scope of QS, but might it be worth adding a
short section on appending something like this to one's local.conf
file before starting the download?

PREMIRRORS_prepend = "\
git://.*/.* file:///home/rpjday/dl/ \n \
svn://.*/.* file:///home/rpjday/dl/ \n \
cvs://.*/.* file:///home/rpjday/dl/ \n \
ftp://.*/.* file:///home/rpjday/dl/ \n \
http://.*/.* file:///home/rpjday/dl/ \n \
https://.*/.* file:///home/rpjday/dl/ \n"

the rationale is that, like myself, a number of people could be
coming to yocto from OE and already have a sizable downloads directory
somewhere on their system that they want to take advantage of and,
with the above, if my downloads directory is up to date, i end up not
having to download a single tarball from the net.

thoughts? is the above relatively complete or is there anything
else i would want to add to that variable? and, again, is it worth
adding a side reference to that for people who could take advantage
of it?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto