From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Introduce cross testing driver for gcc-cross
Date: Tue, 13 Dec 2011 18:54:58 -0800 [thread overview]
Message-ID: <cover.1323831034.git.raj.khem@gmail.com> (raw)
Hi
One patch makes the eglibc testing driver a bit more informative
and cleans the tests before running
Second patch introduces generating a script which will drive
cross testing of gcc. This script is generated as part of do_compile
task and virtually one can test bootstrapping versions of gcc as
well if need be but mostly gcc-cross makes most sense since thats
the one we use all the time.
The following changes since commit b9dfccc018f32a47fc045f35d5f53d7269d791ed:
gdk-pixbuf: Ensure the binaries can be relocated (2011-12-13 18:00:18 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/gcc-cross-testing
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/gcc-cross-testing
Khem Raj (2):
eglibc-testing: Clean the test before running them
gcc-cross: Add cross testing driver for running regression testsuites
meta/recipes-core/eglibc/eglibc-testing.inc | 36 ++++++++++-
meta/recipes-devtools/gcc/gcc-cross.inc | 91 ++++++++++++++++++++++++++-
2 files changed, 125 insertions(+), 2 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-12-14 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 2:54 Khem Raj [this message]
2011-12-14 2:55 ` [PATCH 1/2] eglibc-testing: Clean the test before running them Khem Raj
2011-12-14 2:55 ` [PATCH 2/2] gcc-cross: Add cross testing driver for running regression testsuites Khem Raj
2011-12-22 17:59 ` [PATCH 0/2] Introduce cross testing driver for gcc-cross Saul Wold
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.1323831034.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.