[yocto] fetch problem during build

[Bruce Ashfield]

On 10-11-30 04:17 PM, Tim Bird wrote:
> 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.

It does sound like that, and you can typically download
and place things in the downloads directory manually
and they'll be picked up and used.

The kernel is no different from other packages in
this sense. I often point the SRC_URI at a local
clone on disk to to save time as well.

I don't have the instructions handy for what exactly
to do to clone via a proxy (others do though, so
hopefully they'll follow up) or download manually.

>
> 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.

For the 0.9 kernel, there is a specific structure
expected for the kernel source tree if you use the
default linux-wrs recipe. You can add to that structure
with your own BSP branches and kernel configuration
without changing the actual source repo.

For a completely different src tree, you can use
some of the other recipes for various other kernels
that use defconfigs and other mechanisms for board
support.

That being said, for 1.0, it will be easier/possible
to point the linux-yocto recipe at another src tree
and have the BSP branching structure automatically
created and bootstrapped for a board, based on any
number of trees.

So depending on what you want to try, there's definitely
something we can do to get you started.

Hope that helps,

Bruce

>
> Any assistance would be appreciated.
>
> Thanks,
>   -- Tim
>
> =============================
> Tim Bird
> Architecture Group Chair, CE Linux Forum
> Senior Staff Engineer, Sony Network Entertainment
> =============================
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto