From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [testsuite patch] Skip py-unwind.exp on x86_64 -m32
Date: Tue, 19 Jul 2016 19:30:00 -0000 [thread overview]
Message-ID: <878twxmnn8.fsf@redhat.com> (raw)
In-Reply-To: <20160718113348.GA25789@host1.jankratochvil.net> (Jan Kratochvil's message of "Mon, 18 Jul 2016 13:33:48 +0200")
On Monday, July 18 2016, Jan Kratochvil wrote:
> In fact I think the cross-arch running of the GDB testsuite should be
> described at
> https://sourceware.org/gdb/wiki/TestingGDB
> but currently it is not. Currently there is only
> https://sourceware.org/gdb/wiki/TestingGDB#Changing_the_compiler_used_to_build_the_testcases
> which uses the simple way I currently use and which breaks the testsuite
> needing the ![is_lp64_target] additional test. Maybe GDB maintainers could
> say that the only valid way to run the testsuite cross-arch is properly
> setting arget_triplet as Markus Metzger suggests. (But then I would need to
> fix many scripts of mine; also not sure if Sergio's Buildbot runs it that
> way.)
I run the cross-arch tests like you, i.e., by specifycing
RUNTESTFLAGS='--target_board=unix/-m32'. It should be possible to hack
our BuildBot to run the tests using arch_triplet as Markus suggested.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2016-07-19 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 14:30 Jan Kratochvil
2016-07-18 10:04 ` Yao Qi
2016-07-18 11:34 ` Jan Kratochvil
2016-07-19 10:06 ` Yao Qi
2016-07-19 18:04 ` Pedro Alves
2016-07-20 11:20 ` Yao Qi
2016-07-20 13:49 ` Pedro Alves
2016-07-20 14:19 ` [commit] " Jan Kratochvil
2016-07-19 19:30 ` Sergio Durigan Junior [this message]
2016-07-20 13:48 ` Pedro Alves
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=878twxmnn8.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=qiyaoltc@gmail.com \
/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