Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [buildbot] Customized build and board file
Date: Thu, 06 Oct 2016 21:08:00 -0000	[thread overview]
Message-ID: <871szt89tz.fsf@redhat.com> (raw)
In-Reply-To: <CAH=s-POtRfVyinbnVnK9sh04m_5BSs+M45DJcuUJKeoRsWy9xg@mail.gmail.com>	(Yao Qi's message of "Wed, 5 Oct 2016 12:01:07 +0100")

On Wednesday, October 05 2016, Yao Qi wrote:

> Hi Sergio,

Hey Yao,

> I want to add a new build slave on gcc114 (aarch64) for aarch32
> gdb testing, that is, gdb and test cases are built by arm-linux-gnueabihf
> compiler.
>
> I want to configure gdb with "--target=arm-linux-gnueabihf
> --host=arm-linux-gnueabihf --build=arm-linux-gnueabihf", and other options,
> and also provide a board file "unix-aarch32.exp" in which
> arm-linux-gnueabihf can be used to compile test cases.
>
> Can we do these things above in our buildbot infrastructure?

Yes, it is possible to provide specific parameters to a builder, so it
should be easy to do this.  About the new board file, I understand that
it is just a workaround due to the limitations you mentioned below, and
as such it is not going to be put upstream, right?  We'd also have to
provide a specific parameter to this builder if we want it to use this
board file.

> Note that this is trade-off among various limitations,
>  - we don't have armv7 devices in gcc compile farm, so we have to emulate
>    on an armv8 machine,
>  - libc6:armhf is not installed on gcc114, so I build the toolchain, and force
>    gdb and test programs use my sysroot.  I am going to raise a request to
>    install libc6:armhf, but it may take a while.

It's been a while since I want to have an ARM buildslave on the
BuildBot, so even with these limitations I still think it's a nice thing
to have.

Thanks for working on this.  I'll have to write special code for this
buildslave, so let me know when you have everything ready.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2016-10-06 21:08 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 [this message]
2016-10-07 14:17   ` Yao Qi
2016-10-13 19:21     ` Sergio Durigan Junior
2016-10-13 19:39       ` Pedro Alves
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=871szt89tz.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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