All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: <yocto@yoctoproject.org>
Subject: fetch problem during build
Date: Tue, 30 Nov 2010 13:17:28 -0800	[thread overview]
Message-ID: <4CF569E8.2000307@am.sony.com> (raw)

Hi all,

I am trying out yocto, and I get the following error during an initial build:

ERROR: Task failed: Fetch failed: Unable to fetch URL git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;fullclone=1;branch=common_pc-standard;name=machine from any source.
NOTE: package linux-wrs-2.6.34+git0+b67e060194a38c6331da1532bd06446087a42b3b_0+0431115c9d720fee5bb105f6a7411efb4f851d26-r12: task do_fetch: Failed
ERROR: Task 476 (/a/home/tbird/work/yocto/poky-laverne-4.0/meta/recipes-kernel/linux/linux-wrs_git.bb, do_fetch) failed with 1

I don't have git access through my corporate firewall, except to kernel.org.
I presume this is the source of the problem.  I read that someone else had problems
with fetching source in CVS.  I suspect that will be a problem as well, since
I don't have CVS access through my corporate firewall either.

I tried the instructions at: https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
(for the git-proxy), but this didn't work. I suspect I don't have a SOCKS
proxy.

In the CVS case above, there appeared to be a workaround to directly download
some files.

Is this possible with the kernel source as well?

Also, I presume I could substitute my own kernel
source, if I wanted to?  Maybe some pointers about how to do what
would be good as well.

Any assistance would be appreciated.

Thanks,
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Network Entertainment
=============================



             reply	other threads:[~2010-11-30 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 21:17 Tim Bird [this message]
2010-11-30 21:30 ` fetch problem during build Bruce Ashfield

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=4CF569E8.2000307@am.sony.com \
    --to=tim.bird@am.sony.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.