public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Christophe Lyon <>
Subject: Re: Arm binutils buildbot workers
Date: Sun, 17 Jul 2022 17:09:04 +0200	[thread overview]
Message-ID: <YtQmECSaFu/> (raw)
In-Reply-To: <>

Hi Christophe,

On Mon, Jul 11, 2022 at 12:54:53PM +0200, Christophe Lyon via Binutils wrote:
> After the GDB builbots, we'd like to add binutils workers for arm64 and
> armhf.  They will be running in Ubuntu containers like the GDB ones:
> At this stage, I'm not sure whether there's interest in having both
> ubuntu-20.04 and 22.04?

If ubuntu-20.04 is an LTS release it might be interesting to have. Is
it an LTS release for Arm (I am not an Ubuntu user and don't know if
they officially support something other than x86_64 as LTS release)?
If not I think just having the latest is better.

> Other question related to binutils: I've noticed there are several buildbot
> flavors, with and without --enable-targets=all.  The machine is powerful so
> we can probably offer to use --enable-targets=all.   Does it make sense?

Yes for 64bit, unclear for 32bit systems. As far as I understand for
32bit systems --enable-targets=all is broken, but only for sim. So we
might have to configure with --enable-targets=all --disable-sim

> What's your opinion?  Or maybe it would be a better use of the resource as a
> try-bot?

Could it be both? The idea behind to user try branches is that you can
run the buildbot builders as if doing a "real" build. There are not
many people using the try branches at the moment, so it isn't really
that much more work (also the configuration is simply adding an
identifical builder to the try-scheduler).



  reply	other threads:[~2022-07-17 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 10:54 Christophe Lyon
2022-07-17 15:09 ` Mark Wielaard [this message]
2022-07-18  9:53   ` Richard Earnshaw
2022-07-18 16:39   ` Christophe Lyon
2022-07-19 21:29     ` Mark Wielaard
2022-07-20  7:32       ` Christophe Lyon
2022-07-20  7:51         ` Luis Machado
  -- strict thread matches above, loose matches on Subject: below --
2022-07-11  9:49 Christophe Lyon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YtQmECSaFu/ \ \ \ \ \

* 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).