[yocto] yocto Digest, Vol 46, Issue 109

Pushpa Teja pushpa at jtechindia.in
Thu Jul 31 01:04:56 PDT 2014


HI,
          iam trying to build yacto for riot board when ever i am giving bitbake getting the below error i strucked in this point please guide me .

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL http://downloads.sourceforge.net/e2fsprogs/e2fsprogs-1.42.8.tar.gz, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
Read error (Connection timed out) in headers.
Read error (Connection timed out) in headers.

ERROR: Function failed: Fetcher failure for URL: 'http://downloads.sourceforge.net/e2fsprogs/e2fsprogs-1.42.8.tar.gz'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/teju/fsl-arm-yocto-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/e2fsprogs/1.42.8-r0/temp/log.do_fetch.9563
ERROR: Task 1746 (/home/teju/fsl-arm-yocto-bsp/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.8.bb, do_fetch) failed with exit code '1'
WARNING: Failed to fetch URL http://gstreamer.freedesktop.org/src/gst-plugins-good/gst-plugins-good-0.10.31.tar.bz2, attempting MIRRORS if available

Thanks &Regards 
pushpa 


Pushpa at JtechIndia.In | Mobile : +91 74188 49193
J-Technologies India LtdCoimbatore | Chennai |  ​​ ​JammuA9, SIDCO Industrial Estate, Coimbatore - 641 021 
Tel : CBE : 0422 4055 555 | CHN : 044 4550 0400 |  ​ JAMMU : ​9086020865 


Www.JtechIndia.Com | Www.Vcare.CoAn ISO Certified Company and the unit of IndoShell Group.

> From: yocto-request at yoctoproject.org
> Subject: yocto Digest, Vol 46, Issue 109
> To: yocto at yoctoproject.org
> Date: Wed, 30 Jul 2014 23:35:58 -0700
> 
> 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. [yocto-docs][PATCH v2] dev-manual: Emphasize that YP supports
>       MIPS64. (Robert P. J. Day)
>    2. Re: [yocto-docs][PATH] Emphasize both 32- and 64-bit MIPS
>       supported. (Khem Raj)
>    3. Re: [yocto-docs][PATCH v2] dev-manual: Emphasize that YP
>       supports MIPS64. (Khem Raj)
>    4. Re: [meta-intel] Why won't my app use multiple threads	under
>       'valleyisland'? (Chris Tapp)
>    5. [meta-mingw] [PATCH] binutils-cross-canadian: Remove
>       nativesdk-flex dependency (Mark Hatle)
>    6. Re: timeline for "official" centos 7 support? (Rifenbark, Scott M)
>    7. Re: why does dev manual, "Supported Board Support Packages",
>       mention only meta-intel? (Rifenbark, Scott M)
>    8. Re: why does dev manual, "Supported Board Support Packages",
>       mention only meta-intel? (Khem Raj)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 30 Jul 2014 16:51:14 -0400 (EDT)
> From: "Robert P. J. Day" <rpjday at crashcourse.ca>
> To: Yocto discussion list <yocto at yoctoproject.org>
> Subject: [yocto] [yocto-docs][PATCH v2] dev-manual: Emphasize that YP
> 	supports MIPS64.
> Message-ID: <alpine.LFD.2.11.1407301650150.31103 at localhost>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> 
> Signed-off-by: Robert P. J. Day <rpjday at crashcourse.ca>
> 
> ---
> 
> diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
> index 6ab93f7..37bc5a2 100644
> --- a/documentation/dev-manual/dev-manual-start.xml
> +++ b/documentation/dev-manual/dev-manual-start.xml
> @@ -36,7 +36,7 @@
>          You can use the OpenEmbedded build system, which uses
>          <link linkend='bitbake-term'>BitBake</link>, to develop complete Linux
>          images and associated user-space applications for architectures based
> -        on ARM, MIPS, PowerPC, x86 and x86-64.
> +        on ARM, MIPS, MIPS64, PowerPC, x86 and x86-64.
>          <note>
>              By default, using the Yocto Project creates a Poky distribution.
>              However, you can create your own distribution by providing key
> 
> -- 
> 
> ========================================================================
> 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: Wed, 30 Jul 2014 15:05:26 -0700
> From: Khem Raj <raj.khem at gmail.com>
> To: "Robert P. J. Day" <rpjday at crashcourse.ca>
> Cc: Yocto discussion list <yocto at yoctoproject.org>
> Subject: Re: [yocto] [yocto-docs][PATH] Emphasize both 32- and 64-bit
> 	MIPS	supported.
> Message-ID:
> 	<CAMKF1srrrrSDakSgSdoORaWxeiO8XN-rn-6N7m1i0nxsu5GiGQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> On Wed, Jul 30, 2014 at 1:48 PM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> >   ok, i should resubmit with "MIPS, MIPS64" then? coming up.
> 
> yes please
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Wed, 30 Jul 2014 15:06:36 -0700
> From: Khem Raj <raj.khem at gmail.com>
> To: "Robert P. J. Day" <rpjday at crashcourse.ca>
> Cc: Yocto discussion list <yocto at yoctoproject.org>
> Subject: Re: [yocto] [yocto-docs][PATCH v2] dev-manual: Emphasize that
> 	YP supports MIPS64.
> Message-ID:
> 	<CAMKF1srucS+EiD5cuRoAah8opR9qHh0wXmMhKz6+B6hFcp6v5w at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> On Wed, Jul 30, 2014 at 1:51 PM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> >
> > Signed-off-by: Robert P. J. Day <rpjday at crashcourse.ca>
> >
> > ---
> >
> > diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
> > index 6ab93f7..37bc5a2 100644
> > --- a/documentation/dev-manual/dev-manual-start.xml
> > +++ b/documentation/dev-manual/dev-manual-start.xml
> > @@ -36,7 +36,7 @@
> >          You can use the OpenEmbedded build system, which uses
> >          <link linkend='bitbake-term'>BitBake</link>, to develop complete Linux
> >          images and associated user-space applications for architectures based
> > -        on ARM, MIPS, PowerPC, x86 and x86-64.
> > +        on ARM, MIPS, MIPS64, PowerPC, x86 and x86-64.
> 
> this is fine however it occurred to me that speciying PPC and PPC64
> would be good too. or powerpc64 and powerpc
> 
> >          <note>
> >              By default, using the Yocto Project creates a Poky distribution.
> >              However, you can create your own distribution by providing key
> >
> > --
> >
> > ========================================================================
> > 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 at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 30 Jul 2014 23:14:29 +0100
> From: Chris Tapp <opensource at keylevel.com>
> To: Darren Hart <dvhart at linux.intel.com>
> Cc: meta-intel at yoctoproject.org, Yocto Project
> 	<yocto at yoctoproject.org>
> Subject: Re: [yocto] [meta-intel] Why won't my app use multiple
> 	threads	under 'valleyisland'?
> Message-ID: <9C9784A3-CA5B-4398-9D33-2D933F6CFC81 at keylevel.com>
> Content-Type: text/plain; charset=us-ascii
> 
> 
> On 29 Jul 2014, at 16:41, Darren Hart <dvhart at linux.intel.com> wrote:
> 
> > On Thu, Jul 24, 2014 at 09:45:41PM +0100, Chris Tapp wrote:
> >> I've got a recipe for an application. This has:
> >> 
> >> 1) A main thread;
> >> 2) An OpenGL ('X' / EGL) graphics rendering thread created using posix threads;
> >> 3) As many threads as required from the graphics thread for GStreamer to service various pipelines.
> >> 
> >> On a Cedartrail platform this happily uses multiple cores.
> > 
> > Major difference here is graphics chip, cedartrail uses EMGD binary drivers,
> > baytrail (valleyisland) uses the open source Intel i965 drivers.
> > 
> > I recently (yesterday) updated meta-intel master and daisy to properly support
> > video acceleration in gstreamer 1.0 - I don't know if this impacts you or not.
> 
> Thanks for the pointer. I'll give it a try and see if it makes a difference.
> 
> > However, if I use the same recipe under a 64-bit valleyisland build (daisy) it
> >> only ever uses a single core (and virtually grinds to a halt).
> >> 
> >> 'top' shows CPU usage for the application never goes above 25% (J1900, so four
> >> cores available). Running four instances of 'yes' gets the total CPU usage to
> >> 100%, so all the cores are available.
> > 
> > Does /proc/cpu list four cores?
> 
> It does.
> 
> I've also found that running the GStreamer pipeline outside of (and at the same time as) my application works as expected - i.e. more CPU resources are used and the application runs at the target loop time, so the system can definitely do what I want...
> 
> > 'taskset' shows that the affinity mask for the application is not restricting
> >> the set of available cores.
> >> 
> >> Umm... Any ideas what's going on here?
> >> 
> >> It looks as if GStreamer and OpenGL are fighting for access to something, but
> >> the pipelines only render to 'fakesink' and 'appsink'.
> >> 
> > 
> > I don't have any GL/GST development experience, so this is likely best taken to
> > those respective lists.
> 
> Thanks, I've already tried that and not got anything back ;-)
> 
> > --
> > Darren
> 
> Chris Tapp
> 
> opensource at keylevel.com
> www.keylevel.com
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Wed, 30 Jul 2014 20:08:55 -0500
> From: Mark Hatle <mark.hatle at windriver.com>
> To: <yocto at yoctoproject.org>
> Subject: [yocto] [meta-mingw] [PATCH] binutils-cross-canadian: Remove
> 	nativesdk-flex dependency
> Message-ID:
> 	<1406768935-15676-1-git-send-email-mark.hatle at windriver.com>
> Content-Type: text/plain
> 
> Flex does not build properly with mingw support, it also does not appear
> to be needed in order to build binutils or the other nativesdk components
> when building for mingw.
> 
> Signed-off-by: Mark Hatle <mark.hatle at windriver.com>
> ---
>  recipes-devtools/binutils/binutils-cross-canadian_2.24.bbappend | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/recipes-devtools/binutils/binutils-cross-canadian_2.24.bbappend b/recipes-devtools/binutils/binutils-cross-canadian_2.24.bbappend
> index 7551868..026c932 100644
> --- a/recipes-devtools/binutils/binutils-cross-canadian_2.24.bbappend
> +++ b/recipes-devtools/binutils/binutils-cross-canadian_2.24.bbappend
> @@ -1,4 +1,5 @@
>  EXTRA_OECONF_append_sdkmingw32 = " --disable-plugins --disable-nls"
>  LDFLAGS_append_sdkmingw32 = " -Wl,-static"
>  
> -DEPENDS_remove_sdkmingw32 = "nativesdk-gettext"
> \ No newline at end of file
> +DEPENDS_remove_sdkmingw32 = "nativesdk-gettext"
> +DEPENDS_remove_sdkmingw32 = "nativesdk-flex"
> -- 
> 1.9.3
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Thu, 31 Jul 2014 05:41:30 +0000
> From: "Rifenbark, Scott M" <scott.m.rifenbark at intel.com>
> To: "Robert P. J. Day" <rpjday at crashcourse.ca>, Yocto discussion list
> 	<yocto at yoctoproject.org>
> Subject: Re: [yocto] timeline for "official" centos 7 support?
> Message-ID:
> 	<41DEA4B02DBDEF40A0F3B6D0DDB1237983FD159C at ORSMSX101.amr.corp.intel.com>
> 	
> Content-Type: text/plain; charset="us-ascii"
> 
> Just before each major release, I run a script that produces the list of validated distros we have tested and support.  So if this is going to be a supported distro, it will get on the list in the manual.
> 
> Scott
> 
> >-----Original Message-----
> >From: yocto-bounces at yoctoproject.org [mailto:yocto-
> >bounces at yoctoproject.org] On Behalf Of Robert P. J. Day
> >Sent: Wednesday, July 30, 2014 12:07 PM
> >To: Yocto discussion list
> >Subject: [yocto] timeline for "official" centos 7 support?
> >
> >
> >  working version of yocto dev manual currently has no mention of centos 7 in
> >the list of supported distributions -- anyone working on validating that?
> >
> >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 at yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Thu, 31 Jul 2014 05:50:09 +0000
> From: "Rifenbark, Scott M" <scott.m.rifenbark at intel.com>
> To: "Robert P. J. Day" <rpjday at crashcourse.ca>, Yocto discussion list
> 	<yocto at yoctoproject.org>
> Subject: Re: [yocto] why does dev manual, "Supported Board Support
> 	Packages", mention only meta-intel?
> Message-ID:
> 	<41DEA4B02DBDEF40A0F3B6D0DDB1237983FD15B5 at ORSMSX101.amr.corp.intel.com>
> 	
> Content-Type: text/plain; charset="us-ascii"
> 
> The bold title of the bullet item should probably not be so restrictive.  The point of the section is to show how to set up the meta-intel repository.  I can re-write this section to indicate the wider BSP support and still use the main meta-intel git clone example.
> 
> Scott
> 
> >-----Original Message-----
> >From: yocto-bounces at yoctoproject.org [mailto:yocto-
> >bounces at yoctoproject.org] On Behalf Of Robert P. J. Day
> >Sent: Wednesday, July 30, 2014 12:25 PM
> >To: Yocto discussion list
> >Subject: [yocto] why does dev manual, "Supported Board Support Packages",
> >mention only meta-intel?
> >
> >
> >  also from current dev manual, chapter 2, there is a bullet point entitled
> >"Supported Board Support Packages" which mentions *only* meta-intel as if its
> >the only such layer.
> >
> >  that seems sort of ... incomplete.
> >
> >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 at yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> ------------------------------
> 
> Message: 8
> Date: Wed, 30 Jul 2014 23:35:25 -0700
> From: Khem Raj <raj.khem at gmail.com>
> To: "Rifenbark, Scott M" <scott.m.rifenbark at intel.com>
> Cc: Yocto discussion list <yocto at yoctoproject.org>
> Subject: Re: [yocto] why does dev manual, "Supported Board Support
> 	Packages", mention only meta-intel?
> Message-ID:
> 	<CAMKF1sqyPbb1-oe23zZ0Rpm31Oxn9pz+yPDDsD_j10h4h2K1FA at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> On Wed, Jul 30, 2014 at 10:50 PM, Rifenbark, Scott M
> <scott.m.rifenbark at intel.com> wrote:
> > The point of the section is to show how to set up the meta-intel repository
> 
> I think it should cover the general case.
> 
> 
> ------------------------------
> 
> -- 
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> End of yocto Digest, Vol 46, Issue 109
> **************************************
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20140731/db3b88f2/attachment.html>


More information about the yocto mailing list