From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Fix for earlier buildtools fix
Date: Fri, 11 Dec 2015 13:51:30 +1300 [thread overview]
Message-ID: <cover.1449794902.git.paul.eggleton@linux.intel.com> (raw)
Hmm, turns out that whilst my earlier buildtools fix did fix the bug,
in question, it still wasn't quite right. Here's the bit I missed doing.
The following changes since commit 192da885e92d3b163b9c4e6b8151c9ecc6062b14:
build-appliance-image: Update to master head revision (2015-12-09 08:49:13 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildtools-fix2
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildtools-fix2
Paul Eggleton (1):
nativesdk-buildtools-perl-dummy: properly set PACKAGE_ARCH
meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb | 2 --
1 file changed, 2 deletions(-)
--
2.5.0
next reply other threads:[~2015-12-11 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 0:51 Paul Eggleton [this message]
2015-12-11 0:51 ` [PATCH 1/1] nativesdk-buildtools-perl-dummy: properly set PACKAGE_ARCH 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=cover.1449794902.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.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