<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 14, 2014 at 11:46 AM, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Fri, Mar 14, 2014 at 11:44 AM, Paul Barker <<a href="mailto:paul@paulbarker.me.uk">paul@paulbarker.me.uk</a>> wrote:<br>
> On 14 March 2014 18:37, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br>
>> On Fri, Mar 14, 2014 at 11:34 AM, Paul Barker <<a href="mailto:paul@paulbarker.me.uk">paul@paulbarker.me.uk</a>> wrote:<br>
>>> I'm stuck using Dylan for a project as I need a 3.2 series kernel.<br>
>>> Building on my current development machine I ran into two failures:<br>
>>><br>
>>> eglibc-initial, do_configure: Make 4.0 isn't recognised<br>
>>><br>
>>> This can be fixed by backporting<br>
>>> a678243d6e4add90c1e9459da42de34d3724db5d (already in Dora).<br>
>>><br>
>>> linux-yocto_3.2: do_patch: Unsupported version of git (1.9.0)<br>
>>><br>
>>> I fixed this by removing git-native from ASSUME_PROVIDED in<br>
>>> meta/conf/bitbake.conf so that git-native-1.8.1.4 was built and used.<br>
>>> That isn't something we should commit in Dylan but may be useful for<br>
>>> others to know the solution if they run into the same problem.<br>
>><br>
>> I think if you also lock your build machine OS along with yocto<br>
>> release, it is less painful.<br>
><br>
> It is definitely less painful. I'm lacking the spare hardware though<br>
> and I want to avoid building inside a VM if I can as I'll be limited<br>
> on how much RAM I can allocate to it and I think the performance will<br>
> take a hit. Thankfully this project isn't far off end-of-life now.<br>
<br>
</div>I use containers. systemd-nspawn goes long way</blockquote></div><br></div><div class="gmail_extra">Yeah, containers (systemd-nspawn, docker) or even a chroot can be invaluable. schroot on a debian machine works quite well too for something as simple as builds. I end up aliasing bb and bitbake to transparently run in the chroot at all times.<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>