[yocto] yocto Digest, Vol 13, Issue 54
Mike Tsukerman
miketsukerman at gmail.com
Mon Oct 31 11:42:01 PDT 2011
On Mon, Oct 31, 2011 at 10:29 PM, <yocto-request at yoctoproject.org> wrote:
> Send yocto mailing list submissions to
> yocto at yoctoproject.org
>
> 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 at yoctoproject.org
>
> You can reach the person managing the list at
> yocto-owner at yoctoproject.org
>
> 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 at crashcourse.ca>
> To: "Rifenbark, Scott M" <scott.m.rifenbark at intel.com>
> Cc: Yocto discussion list <yocto at yoctoproject.org>
> Subject: Re: [yocto] any objection to adding a PREMIRRORS section to
> the QS guide?
> Message-ID:
> <alpine.DEB.2.02.1110311150440.7448 at localhost6.localdomain6>
> 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 at freescale.com>
> To: Mike Tsukerman <miketsukerman at gmail.com>
> Cc: "yocto at yoctoproject.org" <yocto at yoctoproject.org>
> Subject: Re: [yocto] root paths in packages
> Message-ID:
> <CAEsOVNd18cWS5JeaxHMLTR9-pr+65bb4s=qc7H_6Prq1PpTzbw at mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Mon, Oct 31, 2011 at 5:57 AM, Mike Tsukerman <miketsukerman at gmail.com>
> 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 at freescale.com> wrote:
> On Mon, Oct 31, 2011 at 11:40 AM, Mike Tsukerman
> <miketsukerman at gmail.com> 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 at intel.com>
> To: "Zanussi, Tom" <tom.zanussi at intel.com>, "yocto at yoctoproject.org"
> <yocto at yoctoproject.org>
> Subject: Re: [yocto] [PATCH 1/2] meta-romley: Fix BSP description in
> romley.conf
> Message-ID:
> <
> 4BD43A85686FC34D819098DB1C3999D9018F70901D at orsmsx502.amr.corp.intel.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Acked-by: Kishore Bodke <Kishore.k.bodke at intel.com>
>
> Thanks
> Kishore.
>
> -----Original Message-----
> From: yocto-bounces at yoctoproject.org [mailto:
> yocto-bounces at yoctoproject.org] On Behalf Of tom.zanussi at intel.com
> Sent: Friday, October 28, 2011 7:00 AM
> To: yocto at yoctoproject.org
> Subject: [yocto] [PATCH 1/2] meta-romley: Fix BSP description in
> romley.conf
>
> From: Tom Zanussi <tom.zanussi at intel.com>
>
> The description still had a reference to Sugar Bay; this changes it to
> Romley.
>
> Signed-off-by: Tom Zanussi <tom.zanussi at intel.com>
> ---
> 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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 31 Oct 2011 10:03:47 -0700
> From: "Bodke, Kishore K" <kishore.k.bodke at intel.com>
> To: "Zanussi, Tom" <tom.zanussi at intel.com>, "yocto at yoctoproject.org"
> <yocto at yoctoproject.org>
> Subject: Re: [yocto] [PATCH 2/2] meta-romley: change references to
> sugarbay in linux-yocto-rt_3.0.bbappend
> Message-ID:
> <
> 4BD43A85686FC34D819098DB1C3999D9018F709021 at orsmsx502.amr.corp.intel.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Acked-by: Kishore Bodke <Kishore.k.bodke at intel.com>
>
> Thanks
> Kishore.
>
> -----Original Message-----
> From: yocto-bounces at yoctoproject.org [mailto:
> yocto-bounces at yoctoproject.org] On Behalf Of tom.zanussi at intel.com
> Sent: Friday, October 28, 2011 7:00 AM
> To: yocto at yoctoproject.org
> Subject: [yocto] [PATCH 2/2] meta-romley: change references to sugarbay in
> linux-yocto-rt_3.0.bbappend
>
> From: Tom Zanussi <tom.zanussi at intel.com>
>
> 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 at intel.com>
> ---
> .../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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 31 Oct 2011 12:12:08 -0500
> From: Mark Hatle <mark.hatle at windriver.com>
> To: <yocto at yoctoproject.org>
> Subject: Re: [yocto] root paths in packages
> Message-ID: <4EAED6E8.3080800 at windriver.com>
> 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 at gmail.com <mailto:miketsukerman at gmail.com>
> > jabber: warzon at jabnet.org <mailto:warzon at jabnet.org>
> > skype: w_a_r_z_o_n
> >
> >
> >
> > _______________________________________________
> > yocto mailing list
> > yocto at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 31 Oct 2011 12:15:28 -0500
> From: Mark Hatle <mark.hatle at windriver.com>
> To: <yocto at yoctoproject.org>
> Subject: Re: [yocto] what's the proper value for BB_NUMBER_THREADS?
> Message-ID: <4EAED7B0.4050909 at windriver.com>
> 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 at crashcourse.ca>
> To: Mark Hatle <mark.hatle at windriver.com>
> Cc: yocto at yoctoproject.org
> Subject: Re: [yocto] what's the proper value for BB_NUMBER_THREADS?
> Message-ID:
> <alpine.DEB.2.02.1110311323050.8545 at localhost6.localdomain6>
> 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 at mlbassoc.com>
> To: "Robert P. J. Day" <rpjday at crashcourse.ca>
> Cc: yocto at yoctoproject.org
> Subject: Re: [yocto] what's the proper value for BB_NUMBER_THREADS?
> Message-ID: <4EAEDD3A.9070601 at mlbassoc.com>
> 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 at freescale.com>
> To: Mike Tsukerman <miketsukerman at gmail.com>
> Cc: "yocto at yoctoproject.org" <yocto at yoctoproject.org>
> Subject: Re: [yocto] root paths in packages
> Message-ID:
> <CAEsOVNeP_tPvsB0BEX2tLXK=sEHP1=NSSEPEX4GVwMiAwr2-_Q at mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Mon, Oct 31, 2011 at 11:40 AM, Mike Tsukerman
> <miketsukerman at gmail.com> 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 at freescale.com> wrote:
> >>
> >> On Mon, Oct 31, 2011 at 5:57 AM, Mike Tsukerman <
> miketsukerman at gmail.com>
> >> 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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> End of yocto Digest, Vol 13, Issue 54
> *************************************
>
--
Best regards, Mike Tsukerman
jabber: miketsukerman at gmail.com
jabber: warzon at jabnet.org
skype: w_a_r_z_o_n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20111031/148266bd/attachment.html>
More information about the yocto
mailing list