From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: arun kumar <arunkr.linux@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: build stuck at cloning GIT Repo.
Date: Fri, 30 Aug 2013 08:34:33 -0400 [thread overview]
Message-ID: <52209159.8070705@windriver.com> (raw)
In-Reply-To: <CABG0-3wCYaJ2Xxt3djtpBrgAW3BBAwU3BcpqewDBQ8GHoM=4vw@mail.gmail.com>
On 13-08-30 02:42 AM, arun kumar wrote:
> My YOcto Project build, The first build is stuck here
> --------------------------------------------------------------------------------------------------
> Loading cache: 100%
> |#################################################################################################################|
> ETA: 00:00:00
> Loaded 1181 entries from dependency cache.
>
> Build Configuration:
> BB_VERSION = "1.19.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "openSUSE-project-12.3"
> TARGET_SYS = "arm-poky-linux-gnueabi"
> MACHINE = "qemuarm"
> DISTRO = "poky"
> DISTRO_VERSION = "1.4+snapshot-20130827"
> TUNE_FEATURES = "armv5 thumb dsp"
> TARGET_FPU = "soft"
> meta
> meta-yocto
> meta-yocto-bsp = "master:b2ff1add530b1fec2fb7f385227a03db47015c37"
>
> NOTE: Resolving any missing task queue dependencies
> NOTE: multiple providers are available for runtime
> libasound-module-bluez (bluez4, bluez5)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match
> libasound-module-bluez
> NOTE: Preparing runqueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> Currently 1 running tasks (1587 of 5917):
> *0: linux-yocto-3.8.13+gitAUTOINC+e7f42a416a_aa76cc2840-r4.2 do_fetch
> (pid 2006)*
> *--------------------------------------------------------------------------------------------------------------*
> **
> and has been so for the past 4-5 Tries, The size of the GIT2 Directory
> seems to increase for sometine,
> The maximum it has gone is 681 MB after which it stopped growing in
> size, i checked wether my Internet was down, but it was all fine as i
> started an OpenWRT build along with it and it was downloading its
> packages smoothly.
> Is there some problem with the GIT server on the Project Side or my ISP ?
> How can i know?
Have you tried cloning the repository manually ? It'll be easier to
pick up on unexpected exits, with the error message from local or
remote being clear.
Cheers,
Bruce
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
prev parent reply other threads:[~2013-08-30 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 6:42 build stuck at cloning GIT Repo arun kumar
2013-08-30 12:34 ` Bruce Ashfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52209159.8070705@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=arunkr.linux@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.