[OE-core] [dylan] Backport request

Chris Larson clarson at kergoth.com
Fri Mar 14 19:06:37 UTC 2014


On Fri, Mar 14, 2014 at 11:46 AM, Khem Raj <raj.khem at gmail.com> wrote:

> On Fri, Mar 14, 2014 at 11:44 AM, Paul Barker <paul at paulbarker.me.uk>
> wrote:
> > On 14 March 2014 18:37, Khem Raj <raj.khem at gmail.com> wrote:
> >> On Fri, Mar 14, 2014 at 11:34 AM, Paul Barker <paul at paulbarker.me.uk>
> wrote:
> >>> I'm stuck using Dylan for a project as I need a 3.2 series kernel.
> >>> Building on my current development machine I ran into two failures:
> >>>
> >>> eglibc-initial, do_configure: Make 4.0 isn't recognised
> >>>
> >>> This can be fixed by backporting
> >>> a678243d6e4add90c1e9459da42de34d3724db5d (already in Dora).
> >>>
> >>> linux-yocto_3.2: do_patch: Unsupported version of git (1.9.0)
> >>>
> >>> I fixed this by removing git-native from ASSUME_PROVIDED in
> >>> meta/conf/bitbake.conf so that git-native-1.8.1.4 was built and used.
> >>> That isn't something we should commit in Dylan but may be useful for
> >>> others to know the solution if they run into the same problem.
> >>
> >> I think if you also lock your build machine OS along with yocto
> >> release, it is less painful.
> >
> > It is definitely less painful. I'm lacking the spare hardware though
> > and I want to avoid building inside a VM if I can as I'll be limited
> > on how much RAM I can allocate to it and I think the performance will
> > take a hit. Thankfully this project isn't far off end-of-life now.
>
> I use containers. systemd-nspawn goes long way


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.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20140314/1eb61a9d/attachment-0002.html>


More information about the Openembedded-core mailing list