From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: [RFC] base.bbclass: add make-native to default dependencies
Date: Mon, 20 Sep 2010 14:47:07 -0400 [thread overview]
Message-ID: <4C97AC2B.1040205@cbnco.com> (raw)
In case the build system is running some ancient make, we can just as
easily build our own make (3.82) to get predictable behaviour. Does
something like this make sense?
diff --git a/classes/base.bbclass b/classes/base.bbclass
index b19eb32..5c6d41d 100644
--- a/classes/base.bbclass
+++ b/classes/base.bbclass
@@ -71,7 +71,7 @@ def base_deps(d):
if not bb.data.getVar('INHIBIT_DEFAULT_DEPS', d):
if (bb.data.getVar('HOST_SYS', d, 1) !=
bb.data.getVar('BUILD_SYS', d, 1)):
- deps += " virtual/${TARGET_PREFIX}gcc virtual/libc "
+ deps += " make-native
virtual/${TARGET_PREFIX}gcc virtual/libc "
elif bb.data.inherits_class('native', d) and \
bb.data.getVar('PN', d, True) not in \
("linux-libc-headers-native",
"quilt-native",
next reply other threads:[~2010-09-20 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 18:47 Michael Smith [this message]
2010-09-20 20:24 ` [RFC] base.bbclass: add make-native to default dependencies Khem Raj
2010-09-21 13:58 ` Michael Smith
2010-09-21 15:47 ` Khem Raj
2010-09-21 16:25 ` Michael Smith
2010-09-21 17:33 ` Holger Freyther
2010-09-21 20:54 ` Michael Smith
2010-09-21 23:34 ` Khem Raj
2010-09-24 19:39 ` [PATCH 1/4] make 3.82: set DEFAULT_PREFERENCE = "-1" Michael Smith
2010-09-24 19:39 ` [PATCH 2/4] base.bbclass: add make-native to default dependencies Michael Smith
2010-09-24 19:39 ` [PATCH 3/4] glibc, glibc-initial: depend on make-native Michael Smith
2010-09-24 19:39 ` [PATCH 4/4] eglibc, eglibc-initial: " Michael Smith
2010-09-25 8:41 ` [PATCH 2/4] base.bbclass: add make-native to default dependencies Paul Menzel
2010-09-25 13:58 ` Michael Smith
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=4C97AC2B.1040205@cbnco.com \
--to=msmith@cbnco.com \
--cc=openembedded-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