From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Build failure on recent yocto download
Date: Thu, 04 Aug 2011 09:17:32 -0700 [thread overview]
Message-ID: <1312474658.2069.3.camel@scimitar> (raw)
In-Reply-To: <4E3A1039.2080108@am.sony.com>
On Wed, 2011-08-03 at 20:21 -0700, Tim Bird wrote:
> On 8/3/2011 5:50 PM, Joshua Lock wrote:
> > On Wed, 2011-08-03 at 17:40 -0700, Joshua Lock wrote:
> >> On Wed, 2011-08-03 at 17:08 -0700, Tim Bird wrote:
> >>> Hi all,
> >>>
> >>> I'm not sure where to report this, but I tried again to build
> >>> Yocto, without success.
> >>>
> >>> I downloaded poky-bernard-4.0.tar.bz2, and followed instructions
> >>> for installing it.
> >>>
> >>> I am using 'MACHINE ?= qemuarm' and doing 'bitbake poky-image-sato'
> >>>
> >>> bitbake error messages follow below.
> >>>
> >>> The first error is a failure to fetch the kernel, and a follow-on
> >>> failure to do a git-clone on the kernel. I'm behind a firewall and
> >>> this is a perennial problem for me. Is there another way to get this
> >>> code? If I do a git-clone on a remote machine and copy it over to
> >>> my development host, where do I put it? (Why did the first http-based
> >>> fetch fail, anyway?) Any help would be appreciated.
> >> We seem to be missing the kernel tarball on our sources mirror... Let me
> >> try and chase that.
> > Chased and caught:
> >
> > joshual@scimitar:~/mess/31
> > $ wget
> > http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz
> > --2011-08-03 17:50:18--
> > http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz
> > Resolving autobuilder.yoctoproject.org... 140.211.169.118
> > Connecting to autobuilder.yoctoproject.org|140.211.169.118|:80...
> > connected.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 449232265 (428M) [application/x-gzip]
> > Saving to: `git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz.1'
> Thanks very much. I'll give it another try.
>
> I've visited the "behind a proxy" help page before. I guess I should
> have checked that for an update before asking.
> -- Tim
We don't mind people asking :-)
Let us know how you get on!
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-08-04 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 0:08 Build failure on recent yocto download Tim Bird
2011-08-04 0:10 ` Tim Bird
2011-08-04 0:33 ` Stewart, David C
2011-08-04 3:29 ` Tim Bird
2011-08-04 0:40 ` Joshua Lock
2011-08-04 0:50 ` Joshua Lock
2011-08-04 3:21 ` Tim Bird
2011-08-04 16:17 ` Joshua Lock [this message]
2011-08-04 1:09 ` Joshua Lock
2011-08-04 1:44 ` Khem Raj
2011-08-04 18:51 ` Tim Bird
2011-08-04 20:22 ` Joshua Lock
2011-08-04 23:39 ` Tim Bird
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=1312474658.2069.3.camel@scimitar \
--to=josh@linux.intel.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.