From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/8] Various QA fixes
Date: Mon, 4 Jul 2011 17:46:25 +0100 [thread overview]
Message-ID: <cover.1309797628.git.richard.purdie@linuxfoundation.org> (raw)
The following changes since commit 2b3bf5350861f62435e2fdf1c56c8a02f4b1b4ac fix
a number of QA warnings/errors. There are a couple of RFC style commits in this mix:
A key change is that functionality is added to insane.bbclass to allow
skipping of individual QA tests by name. It needs two existing users (elfutils and u-boot)
to specify which QA tests they want to skip (I'm working on a patch). Any external
layer using that variable would need to update and I can't decide if that is a
drawback or a feature.
Also a gettext change I'm testing to see which approach performs best is included. A final decision on that will depend on the performance test results (thanks go to paul for hightlighting the impact of that git-native depenedency).
Also included is a gcc libiberty fix (yocto #1199).
They are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rpurdie/master
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rpurdie/master
Richard Purdie (5):
gcc: Fix removal of libiberty.a
gettext: Disable both git and cvs for autopoint's archive format.
gcc: Remove unneeded module .la file and .so link
insane.bbclass: Allow INSANE_SKIP to work on a per test basis
lttng-viewer: Fixup various QA warnings and a false positive
Richard Purdie (3):
oprofile: Fix QA warnings
libgsmd: Fix QA warnings
gcc-package-cross: Switch to using pattern matching to detect when to
stash libgcc into the sysroot
meta/classes/insane.bbclass | 37 +++++++++++---------
meta/recipes-connectivity/gsm/gsmd.inc | 26 ++++++++++----
meta/recipes-core/gettext/gettext_0.18.1.1.bb | 7 ++--
meta/recipes-devtools/gcc/gcc-4.6.inc | 2 +-
.../gcc/gcc-cross-intermediate.inc | 4 +-
meta/recipes-devtools/gcc/gcc-package-cross.inc | 30 ++++++++-------
meta/recipes-devtools/gcc/gcc-package-target.inc | 6 ++-
meta/recipes-devtools/gcc/gcc_4.5.1.bb | 2 +-
meta/recipes-kernel/lttng/lttng-viewer_0.12.38.bb | 6 ++-
meta/recipes-kernel/oprofile/oprofile_0.9.6.bb | 4 ++
10 files changed, 75 insertions(+), 49 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-07-04 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 16:46 Richard Purdie [this message]
2011-07-04 16:46 ` [PATCH 1/8] oprofile: Fix QA warnings Richard Purdie
2011-07-04 16:46 ` [PATCH 2/8] libgsmd: " Richard Purdie
2011-07-04 16:46 ` [PATCH 3/8] gcc: Fix removal of libiberty.a Richard Purdie
2011-07-04 16:46 ` [PATCH 4/8] gettext: Disable both git and cvs for autopoint's archive format Richard Purdie
2011-07-04 16:46 ` [PATCH 5/8] gcc: Remove unneeded module .la file and .so link Richard Purdie
2011-07-04 16:46 ` [PATCH 6/8] insane.bbclass: Allow INSANE_SKIP to work on a per test basis Richard Purdie
2011-07-04 16:46 ` [PATCH 7/8] lttng-viewer: Fixup various QA warnings and a false positive Richard Purdie
2011-07-04 16:46 ` [PATCH 8/8] gcc-package-cross: Switch to using pattern matching to detect when to stash libgcc into the sysroot Richard Purdie
2011-07-05 10:25 ` [PATCH 0/8] Various QA fixes Richard Purdie
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.1309797628.git.richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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