From: Mihai Lindner <mihaix.lindner@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: bitbake error
Date: Fri, 13 Jul 2012 14:08:57 +0300 [thread overview]
Message-ID: <500001C9.1040705@linux.intel.com> (raw)
In-Reply-To: <4FFFCBD3.7080809@windriver.com>
On 2012-07-13 10:18, Robert Yang wrote:
>
>
> On 07/12/2012 06:53 PM, Girija B wrote:
>> Hello,
>>
>> I have installed bitbake and open embedded environment , when i run the command : bitbake meta-toolchain-qte , am getting the following error :
>> Pseudo is not present but is required, building this first before the main build
>> ERROR: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: Fetch command export HOME="/home/girija"; export SSH_AUTH_SOCK="/tmp/keyring-vMpejY/ssh"; export GIT_CONFIG="/home/girija/mft/platform/build/tmp-eglibc/sysroots/i686-linux/etc/gitconfig"; export PATH="/home/girija/mft/platform/build/tmp-eglibc/sysroots/i686-linux/usr/bin/armv5te-oe-linux-gnueabi:/home/girija/mft/platform/build/tmp-eglibc/sysroots/tonga2/usr/bin/crossscripts:/home/girija/mft/platform/build/tmp-eglibc/sysroots/i686-linux/usr/sbin:/home/girija/mft/platform/build/tmp-eglibc/sysroots/i686-linux/usr/bin:/home/girija/mft/platform/build/tmp-eglibc/sysroots/i686-linux/sbin:/home/girija/mft/platform/build/tmp-eglibc/sysroots/i686-linux//bin:/home/girija/mft/platform/3rd-party/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/girija/mft/platform/3rd-party/openembedded-core/scripts"; git ls-r
!
> em!
>> ote ssh://git@savage-git:10221/var/lib/git/joule/joule-test-app master could not be run:
>
> There is a "git ls-rem!", maybe this is a typo?
>
> // Robert
>
>> None
>> ERROR: Command execution failed: Exited with 1
>>
>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>
>>
>>
>> please help me in solving this
>>
>> Thanks,
>> Girija.B
>> Larsen & Toubro Limited
>>
>> www.larsentoubro.com
>>
>> This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>>
>> _______________________________________________
>> bitbake-devel mailing list
>> bitbake-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
>>
>>
>
>
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
>
>
I would be more worried about the "ssh://git@*savage-git*:10221" part.
Is that from a custom(ized) recipe?
--
Mihai Lindner
Yocto Project
next prev parent reply other threads:[~2012-07-13 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 10:53 bitbake error Girija B
2012-07-13 7:18 ` Robert Yang
2012-07-13 11:08 ` Mihai Lindner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 4:30 Solomon Kinard
2019-09-26 4:47 Bitbake Error SHOAIB MUHAMMAD
2019-09-26 21:08 ` Richard Purdie
2020-02-21 11:23 bitbake error Iñigo Vicente Waliño
2020-02-21 19:53 ` Khem Raj
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=500001C9.1040705@linux.intel.com \
--to=mihaix.lindner@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox