Re: How to force the use of git-native?

[Gary Thomas <gary@mlbassoc.com>]

On 2013-12-12 09:37, Paul Eggleton wrote:
> On Thursday 12 December 2013 09:31:10 Gary Thomas wrote:
>> On 2013-12-12 09:28, Gary Thomas wrote:
>>> On 2013-12-12 09:20, Paul Eggleton wrote:
>>>> Hi Gary,
>>>>
>>>> On Thursday 12 December 2013 08:06:31 Gary Thomas wrote:
>>>>> I've found that the latest bitbake fetcher changes (require
>>>>> the use of branch names) fails with older versions of git.
>>>>> I have a Fedora 13 machine which I routinely use to build
>>>>> my Yocto projects that has git version 1.7.7.6.  On that machine,
>>>>> all git fetches fail, no matter what.  On my Ubuntu builder
>>>>> which has git 1.7.9.4, all is OK.
>>>>>
>>>>> I see that there is a git recipe in OE-core.  How can I force
>>>>> it to be built and used where the host's native git is inadequate?
>>>>
>>>> The solution we provide for this kind of situation is buildtools-tarball,
>>>> as described here (linked from the QS guide as well):
>>>>
>>>> http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#requi
>>>> red-git-tar-and-python-versions>
>>> Thanks, I'll give this a go.
>>
>> Oops, looks like I have a circular dependency problem since trying to make
>> the buildtools-tarball actually needs a working version of git??
>
> I don't think it's reasonable to expect to build buildtools-tarball on a
> system that isn't capable of building at the moment; you should just download
> a prebuilt version as linked from the manual section above *or* build it on
> another machine.

Too bad that pointer is only for x86_64 hosts (mine is i386 only)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------