All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florin <flocirel@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: do_fetch error with gcc-cross-initial_4.7
Date: Wed, 19 Sep 2012 12:02:28 +0300	[thread overview]
Message-ID: <50598A24.1040503@gmail.com> (raw)
In-Reply-To: <CAMKF1sqhPaHkiOn5uTiF6mQixoatRL8queN6XX5AvQaxL1nvzg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2728 bytes --]

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 
> <mailto: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 
> <http://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 <mailto:poky@yoctoproject.org>
> >> https://lists.yoctoproject.org/listinfo/poky
> >
> > _______________________________________________
> > poky mailing list
> > poky@yoctoproject.org <mailto:poky@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/poky
> > 


[-- Attachment #2: Type: text/html, Size: 4119 bytes --]

  reply	other threads:[~2012-09-19  9:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 21:35 do_fetch error with gcc-cross-initial_4.7 Florin
2012-08-23  7:29 ` Tomas Frydrych
2012-08-23 14:09   ` Florin
2012-08-23 15:35     ` Khem Raj
2012-09-19  9:02       ` Florin [this message]
2012-09-24 10:51         ` Richard Purdie
2012-09-24 11:19           ` Gary Thomas
2012-09-24 11:31             ` [poky] " Martin Jansa
2012-09-24 12:24             ` Gary Thomas

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=50598A24.1040503@gmail.com \
    --to=flocirel@gmail.com \
    --cc=poky@yoctoproject.org \
    --cc=raj.khem@gmail.com \
    /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.