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
>