From: Yao Qi <qiyaoltc@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: AArch64 GDB buildbot
Date: Tue, 14 Jun 2016 07:33:00 -0000 [thread overview]
Message-ID: <CAH=s-PPxATKU6LR3am_X_z19bj0MEPyHPnv5BvHs2b+jPzXb5w@mail.gmail.com> (raw)
In-Reply-To: <87a8ipuhuq.fsf@redhat.com>
On Mon, Jun 13, 2016 at 6:19 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
>> Thanks. I want to run gdb tests for aarch64-linux in four modes,
>> {unix,native-gdbserver} x {aarch64, arm}. In "arm", the test case is compiled
>> by arm-linux compiler, but GDB and GDBserver is still aarch64 program.
>
> OK, then you're gonna have to provide the full configure, make and make
> check lines for me so that I can adjust our configuration, please.
>
I take a look at files at git://git.sergiodj.net/gdb-buildbot.git, and
don't know how
to support multi-arch testing in aarch64 (aarch64 gcc doesn't accept -m32
option to generate arm code). Let us step up simple configurations first.
The machine we want to use is gcc115.fsffrance.org. The Linux is ubuntu
trusty. The configure option I use is "--disable-binutils
--disable-gprof --disable-gold --disable-gas --disable-ld". Then,
"make" and "make check". I also want
to test with native-gdbserver, so make check
RUNTESTFLAGS="--target_board=native-gdbserver". This should be
similar to other existing buildbot
slave settings.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-06-14 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 12:45 Yao Qi
2016-06-13 15:40 ` Sergio Durigan Junior
2016-06-13 16:14 ` Yao Qi
2016-06-13 17:19 ` Sergio Durigan Junior
2016-06-14 7:33 ` Yao Qi [this message]
2016-06-21 1:09 ` Sergio Durigan Junior
2016-06-21 7:46 ` Yao Qi
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='CAH=s-PPxATKU6LR3am_X_z19bj0MEPyHPnv5BvHs2b+jPzXb5w@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).