From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Misc fixes
Date: Wed, 22 Mar 2017 20:37:58 -0700 [thread overview]
Message-ID: <cover.1490240196.git.raj.khem@gmail.com> (raw)
clang finds couple of more issues to weed out
The following changes since commit d1d55041e38b12d40f896834b56475ea19a6047f:
sstate: Ensure installation directory is empty before execution (2017-03-22 10:12:10 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/pu
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=kraj/pu
Khem Raj (2):
db: Fix atomic function namespace clash with clang builtins
libvorbis: Contain gcc specific compiler flags using configure option
.../libvorbis/0001-configure-Check-for-clang.patch | 56 ++++++++++++++++++++++
.../libvorbis/libvorbis_1.3.5.bb | 4 +-
...me-local-__atomic_compare_exchange-to-avo.patch | 45 +++++++++++++++++
meta/recipes-support/db/db_5.3.28.bb | 1 +
4 files changed, 105 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-multimedia/libvorbis/libvorbis/0001-configure-Check-for-clang.patch
create mode 100644 meta/recipes-support/db/db/0001-atomic-Rename-local-__atomic_compare_exchange-to-avo.patch
--
2.12.1
next reply other threads:[~2017-03-23 3:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 3:37 Khem Raj [this message]
2017-03-23 3:38 ` [PATCH 1/2] db: Fix atomic function namespace clash with clang builtins Khem Raj
2017-03-23 3:38 ` [PATCH 2/2] libvorbis: Contain gcc specific compiler flags using configure option Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2012-05-16 18:11 [PATCH 0/2] Misc fixes nitin.a.kamble
2012-04-26 22:53 nitin.a.kamble
2012-05-01 18:32 ` Saul Wold
2012-04-13 4:43 [PATCH 0/2] Misc Fixes nitin.a.kamble
2012-01-19 13:59 [PATCH 0/2] Misc fixes Paul Eggleton
2011-07-21 21:08 [PATCH 0/2] Misc Fixes nitin.a.kamble
2011-07-22 15:41 ` Saul Wold
2011-07-21 9:29 nitin.a.kamble
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.1490240196.git.raj.khem@gmail.com \
--to=raj.khem@gmail.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