From: Saul Wold <sgw@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>,
openembedded-core <openembedded-core@lists.openembedded.org>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [dylan] Backport request
Date: Fri, 14 Mar 2014 11:57:09 -0700 [thread overview]
Message-ID: <53235105.4060205@linux.intel.com> (raw)
In-Reply-To: <CANyK_8dJY0nbt6aNeLYeRggTHXj9qiGbSemngbZAdf7LU_KzCQ@mail.gmail.com>
On 03/14/2014 11:34 AM, Paul Barker 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.
>
Can't you use the buildtools tarball? It includes the right version of
make and git.
Sau!
> Thanks,
>
next prev parent reply other threads:[~2014-03-14 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 18:34 [dylan] Backport request Paul Barker
2014-03-14 18:37 ` Khem Raj
2014-03-14 18:44 ` Paul Barker
2014-03-14 18:46 ` Khem Raj
2014-03-14 19:06 ` Chris Larson
2014-03-14 19:11 ` Paul Barker
2014-03-14 19:13 ` Chris Larson
2014-03-14 19:16 ` Khem Raj
2014-03-14 19:37 ` Paul Barker
2014-03-14 18:57 ` Saul Wold [this message]
2014-03-14 19:11 ` Jack Mitchell
2014-03-14 19:15 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2015-01-08 18:13 Paul Barker
2015-01-12 12:04 ` Paul Eggleton
2015-09-18 7:52 [dylan] Backport Request Paul Barker
2015-09-18 9:40 ` Paul Eggleton
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=53235105.4060205@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=paul@paulbarker.me.uk \
/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.