From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 33A38E002AC for ; Wed, 19 Sep 2012 02:02:33 -0700 (PDT) Received: by pbbrq13 with SMTP id rq13so2380507pbb.35 for ; Wed, 19 Sep 2012 02:02:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=SF6gHOiwP9Fsasyq+AYnO4C39ZXGC7GlXy3XtDWIcb4=; b=L4R2N4ZSVrY/JG4bBvUZoszkkM/GcptIdZahthfHce2qqleQDAScyQB0ds8VgwPPUD Bmpub2j6eYUj1g34s3eep4Vm4qqSsvg5RqOmkxjUSvhsTZozC+ZHHlG4uNCCFjeWA4j9 nudKjEX+PYqdFCCJG+lJZGw5tDvBkdhCQfchilvn8k+WsIDeUNFPe/JAIvIC/gGqu3N3 43582Xc2jVeAhb2i/1VlChzbKGYbiGKN92Y8KDJQaE4Y2e4WmtaLVyz6/tQLUMEJl34L GVYOrddOeOln+/H9+r2b87kEFG3QU2q3rXShAB/8nfKlqc0QJWnxuIxsbXxC9svFFRAG hAMw== Received: by 10.68.226.38 with SMTP id rp6mr5719974pbc.116.1348045350828; Wed, 19 Sep 2012 02:02:30 -0700 (PDT) Received: from [128.224.170.241] ([89.121.200.106]) by mx.google.com with ESMTPS id f9sm649616paz.1.2012.09.19.02.02.28 (version=SSLv3 cipher=OTHER); Wed, 19 Sep 2012 02:02:29 -0700 (PDT) Message-ID: <50598A24.1040503@gmail.com> Date: Wed, 19 Sep 2012 12:02:28 +0300 From: Florin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Khem Raj References: <503550B4.6060708@gmail.com> <5035DBF4.2020201@r-finger.com> <503639B2.4000605@gmail.com> In-Reply-To: Cc: "poky@yoctoproject.org" Subject: Re: do_fetch error with gcc-cross-initial_4.7 X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion & patch submission for meta-yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Sep 2012 09:02:33 -0000 Content-Type: multipart/alternative; boundary="------------060000050406060408090009" --------------060000050406060408090009 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Trying to build something today and still takes forever and crashes at fetch. Looking at the gcc-4.7.inc I see it's still from git. What would the resolution be for this issue? Thank you On 08/23/2012 06:35 PM, Khem Raj wrote: > > > On Thursday, August 23, 2012, Florin > wrote: > > On 08/23/2012 10:29 AM, Tomas Frydrych wrote: > >> > >> Hi, > >> > >> On 22/08/12 22:35, Florin wrote: > >>> > >>> ERROR: Function failed: Fetcher failure for URL: > >>> > 'git://github.com/mirrors/gcc.git;branch=gcc-4_7-branch;protocol=git > '. > >>> Unable to fetch URL from any source. > >>> > >>> > >>> After the build stops with this error, retrying the bitbake command to > >>> produce the rootfs fetches gcc successfully and gcc (and the rest > of the > >>> packages) is compiled just fine. > >>> Is there anybody else seeing this behavior? > >> > >> FWIW, over the last few days I have seen intermittent fetch failures > >> from various packages that pull source from github; they pretty much > >> always go away on the next attempt; I assume it's github's fault. > > > > Hi Tomas, > > thanks for your answer. The problem I am seeing is that it always > behaves like this: in the stages of creating the rootfs it gets to the > fetching of gcc cross initial, this stalls a while (tens of minutes) > in which time bitbake fetches (all kind of native and target packages) > and compiles native packages and it throws an error at the point where > the dependency chain would have had gcc cross initial compiled and > ready to be used by other packages. After that, rerunning the bitbake > command to create the rootfs fetches successfully gcc and the build > finishes. So I am always seeing this behavior: first fetch fails, > second fetch works. Always like this, never had to try a third time to > fetch gcc. That is why I am not suspecting especially a problem with > github but rather the way bitbake tries the mirrors for gcc. > > > > Git archive for gcc is in terabytes so it will take long time to fetch > it. I have sent a patch to switch back to Svn in src_URI > That should avoid long delays in fetching gcc srcs > > Thanks, > > Florin > >> > >> Tomas > >> _______________________________________________ > >> poky mailing list > >> poky@yoctoproject.org > >> https://lists.yoctoproject.org/listinfo/poky > > > > _______________________________________________ > > poky mailing list > > poky@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/poky > > --------------060000050406060408090009 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Trying to build something today and still takes forever and crashes at fetch. Looking at the gcc-4.7.inc I see it's still from git.
What would the resolution be for this issue?

Thank you

On 08/23/2012 06:35 PM, Khem Raj wrote:


On Thursday, August 23, 2012, Florin <flocirel@gmail.com> wrote:
> On 08/23/2012 10:29 AM, Tomas Frydrych wrote:
>>
>> Hi,
>>
>> On 22/08/12 22:35, Florin wrote:
>>>
>>> ERROR: Function failed: Fetcher failure for URL:
>>> 'git://github.com/mirrors/gcc.git;branch=gcc-4_7-branch;protocol=git'.
>>> Unable to fetch URL from any source.
>>>
>>>
>>> After the build stops with this error, retrying the bitbake command to
>>> produce the rootfs fetches gcc successfully and gcc (and the rest of the
>>> packages) is compiled just fine.
>>> Is there anybody else seeing this behavior?
>>
>> FWIW, over the last few days I have seen intermittent fetch failures
>> from various packages that pull source from github; they pretty much
>> always go away on the next attempt; I assume it's github's fault.
>
> Hi Tomas,
> thanks for your answer. The problem I am seeing is that it always behaves like this: in the stages of creating the rootfs it gets to the fetching of gcc cross initial, this stalls a while (tens of minutes) in which time bitbake fetches (all kind of native and target packages) and compiles native packages and it throws an error at the point where the dependency chain would have had gcc cross initial compiled and ready to be used by other packages. After that, rerunning the bitbake command to create the rootfs fetches successfully gcc and the build finishes. So I am always seeing this behavior: first fetch fails, second fetch works. Always like this, never had to try a third time to fetch gcc. That is why I am not suspecting especially a problem with github but rather the way bitbake tries the mirrors for gcc.
>

Git archive for gcc is in terabytes so it will take long time to fetch it. I have sent a patch to switch back to Svn in src_URI
That should avoid long delays in fetching gcc srcs
> Thanks,
> Florin
>>
>> Tomas
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>

--------------060000050406060408090009--