From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Jim Rucker <jrucker@altera.com>
Subject: Re: error with bb.fetch2.get_srcrev(d)
Date: Fri, 4 May 2012 16:46:54 -0400 [thread overview]
Message-ID: <4FA4403E.8010000@windriver.com> (raw)
In-Reply-To: <CAEsOVNfDA9rcQ1dshyKBq=rCk4nmqsBTQ0QvNL9jxa5SO52VBg@mail.gmail.com>
On 12-05-04 12:08 PM, McClintock Matthew-B29882 wrote:
> On Fri, May 4, 2012 at 10:46 AM, Jim Rucker<jrucker@altera.com> wrote:
>> In the project that I'm working on we have a recipes-bsp and recipes-kernel, and
>> when I try to build virtual/kernel I'm getting the following error. It looks to
>> me like it's trying to get the git from our u-boot server so it can find the
>> version, but at this point I'm trying to build the kernel, not u-boot. So, is
>> there a way to build it independently, and if so how do I isolate the issue?
>> bitbake -DDD doesn't provide any additional info
>>
>>
>>
>> ERROR: Failure expanding variable SRCPV, expression was
>> ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher
>> failure for URL: 'None'. Fetch command export HOME="/home/jrucker"; export
>> SSH_AGENT_PID="1461"; export SSH_AUTH_SOCK="/tmp/keyring-yphCY1/ssh"; export
>> GIT_CONFIG="/home/jrucker/poky/6.0/poky-edison-6.0/build/tmp/sysroots/i686-
>> linux/usr/etc/gitconfig"; export PATH="/home/jrucker/poky/6.0/poky-edison-
>> 6.0/build/tmp/sysroots/i686-linux/usr/bin/armv7a-vfp-neon-poky-linux-
>> gnueabi:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/build/tmp/sysroots/socfpga5xs1/usr/bin/crossscripts:/home/jrucker/poky/6.0/p
>> oky-edison-6.0/build/tmp/sysroots/i686-
>> linux/usr/sbin:/home/jrucker/poky/6.0/poky-edison-6.0/build/tmp/sysroots/i686-
>> linux/usr/bin:/home/jrucker/poky/6.0/poky-edison-6.0/build/tmp/sysroots/i686-
>> linux/sbin:/home/jrucker/poky/6.0/poky-edison-6.0/build/tmp/sysroots/i686-
>> linux//bin:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/bitbake/bin/:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/scripts:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/bitbake/bin/:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/scripts:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/bitbake/bin/:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/scripts:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/bitbake/bin/:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/scripts:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/bitbake/bin/:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/scripts:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/bitbake/bin/:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sb
>> in:/usr/bin:/sbin:/bin:/usr/games:/home/jrucker/poky/6.0/poky-edison-
>> 6.0/scripts"; git ls-remote ssh://git@ec2-67-102-16-93.compute-
>> 1.amazonaws.com/uboot.git socfpga5xs1_v2011.12 failed with signal 128, output:
>> Permission denied (publickey).
>> fatal: The remote end hung up unexpectedly
>
> Does your u-boot SRCREV = ${AUTOREV}? You could try picking a specific
> SHA so it does not have to check for the latest each time.
This is definitely a good suggestion. If you aren't using AUTOREV, then
something else is triggering the fetcher. All of your parsed recipes can
trigger fetchers, whether or not it is precisely what you are building,
since the upstream sources are part of determining what needs to be
rebuilt. It was a surprising (to me), but fundamental thing that happens,
and I've just gotten used to it :)
Richard could probably correct my description above, or provide more
options.
Bruce
>
> -M
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-05-04 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 15:46 error with bb.fetch2.get_srcrev(d) Jim Rucker
2012-05-04 16:08 ` McClintock Matthew-B29882
2012-05-04 20:46 ` Bruce Ashfield [this message]
2012-05-04 20:57 ` Jim Rucker
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=4FA4403E.8010000@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=B29882@freescale.com \
--cc=jrucker@altera.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.