Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/3] Update the sanity check and make
Date: Mon, 24 Jun 2013 09:45:46 -0500	[thread overview]
Message-ID: <1372085149-30510-1-git-send-email-mark.hatle@windriver.com> (raw)

The sanity check should also look for the broken version of make.

Our version of make also happens to be broken, so fix that as well.

And add nativesdk-make to the buildtools-tarball, to assist people with
broken buildtools.  (Note, current Fedora and CentOS machines contain
the broken make as well.  A patch is pending in the Fedora community
to update this.)

Mark Hatle (3):
  sanity.bbclass: Check for the known broken version of make
  make: Fix second part of bug Savannah 30612
  buildtools-tarball: Add nativesdk-make

 meta/classes/sanity.bbclass                        | 39 +++++++++++++++
 meta/recipes-core/meta/buildtools-tarball.bb       |  3 +-
 .../make-savannah-bug30612-fix_white_space.patch   | 58 ++++++++++++++++++++++
 meta/recipes-devtools/make/make_3.82.bb            |  5 +-
 4 files changed, 102 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-devtools/make/make-3.82/make-savannah-bug30612-fix_white_space.patch

-- 
1.8.3.1



             reply	other threads:[~2013-06-24 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 14:45 Mark Hatle [this message]
2013-06-24 14:45 ` [PATCH 1/3] sanity.bbclass: Check for the known broken version of make Mark Hatle
2013-06-24 22:09   ` Saul Wold
2013-06-25  2:06     ` Mark Hatle
2013-06-25 11:20       ` Martin Jansa
2013-06-25 14:12         ` Mark Hatle
2013-06-25 14:26           ` Martin Jansa
2013-06-24 14:45 ` [PATCH 2/3] make: Fix second part of bug Savannah 30612 Mark Hatle
2013-06-24 14:45 ` [PATCH 3/3] buildtools-tarball: Add nativesdk-make Mark Hatle

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=1372085149-30510-1-git-send-email-mark.hatle@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@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