Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [buildbot] Customized build and board file
Date: Thu, 13 Oct 2016 19:39:00 -0000	[thread overview]
Message-ID: <9a54ce4e-a094-f029-0177-ae05633f2aa2@redhat.com> (raw)
In-Reply-To: <871szk5a2s.fsf@redhat.com>

On 10/13/2016 08:21 PM, Sergio Durigan Junior wrote:
> 
> So, I'm trying to decide what is the best way to use the board file.  It
> needs to be placed in the gdb/testsuite/boards/ directory, right?  

You can run tests against a board file that is elsewhere.
See the steps described here:

 https://sourceware.org/gdb/wiki/TestingGDB#Testing_gdbserver_in_a_remote_cross-target_configuration

~~~
    Create an empty file named site.exp.
    Create a directory named boards in the same location as site.exp.
    Create a file named remote-gdbserver.exp in the boards directory (see below).
    Set the DEJAGNU environment variable to point to the empty site.exp.
    Run the testsuite with make check-gdb RUNTESTFLAGS="--target_board remote-gdbserver". 
~~~

That used to be the only way people could run tests with the
gdbserver board files before "magic" was added that made it possible
to import the files into the tree.

> But
> the way BuildBot works is by making a full clone of the repository on
> for every build.  I *might* be able to upload the file to the ARM slave,
> but that would require a hack that I'm trying to avoid.

Thanks,
Pedro Alves


  reply	other threads:[~2016-10-13 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 11:01 Yao Qi
2016-10-06 21:08 ` Sergio Durigan Junior
2016-10-07 14:17   ` Yao Qi
2016-10-13 19:21     ` Sergio Durigan Junior
2016-10-13 19:39       ` Pedro Alves [this message]
2016-10-13 19:54         ` Sergio Durigan Junior
2016-10-14 13:33           ` 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=9a54ce4e-a094-f029-0177-ae05633f2aa2@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    --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