From: Mark Wielaard <mark@klomp.org>
To: Mohammad-Reza Nabipoor <mnabipoor@gnu.org>
Cc: buildbot@sourceware.org, poke-devel@gnu.org
Subject: Re: [PATCH builder.git] master.cfg: add GNU poke builder
Date: Thu, 24 Nov 2022 13:11:08 +0100 [thread overview]
Message-ID: <b31833e713a76d57975033932f183918c8f562a2.camel@klomp.org> (raw)
In-Reply-To: <Y36Apxjj/pYArZnV@schwinger>
Hi Mohammad-Reza,
On Wed, 2022-11-23 at 21:20 +0100, Mohammad-Reza Nabipoor wrote:
> On Wed, Nov 23, 2022 at 06:44:28PM +0100, Mark Wielaard wrote:
> > Lets at least add a debian-i386 builder (as attached).
> > Please feel free to request other arches.
>
> Thanks for these builders.
> debian-armhf is also very useful for us (because it uncovered
> lot of bugs during the release of poke 2.0).
Unfortunately the armhf workers we currently have are either based on
debian old-stable (debian-armhf) which is too old to build poke, or
reserved for building full gcc and gdb builds (ubuntu22_04-armhf and
armhf-ubuntu22_04). I'll see if I can upgrade the debian-armhf board,
but that might take some time.
Cheers,
Mark
next prev parent reply other threads:[~2022-11-24 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 23:36 Arsen Arsenović
2022-11-20 11:48 ` Jose E. Marchesi
2022-11-20 12:21 ` Arsen Arsenović
2022-11-20 13:17 ` Frank Ch. Eigler
2022-11-20 14:43 ` Arsen Arsenović
2022-11-20 15:31 ` Frank Ch. Eigler
2022-11-20 16:05 ` Arsen Arsenović
2022-11-20 14:12 ` Jose E. Marchesi
2022-11-23 0:37 ` Mark Wielaard
2022-11-23 11:53 ` Jose E. Marchesi
2022-11-23 17:44 ` Mark Wielaard
2022-11-23 20:20 ` Mohammad-Reza Nabipoor
2022-11-24 12:11 ` Mark Wielaard [this message]
2022-11-28 16:48 ` Frank Ch. Eigler
2022-11-28 19:09 ` Arsen Arsenović
2022-11-28 21:53 ` Frank Ch. Eigler
2022-11-29 11:55 ` Mohammad-Reza Nabipoor
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=b31833e713a76d57975033932f183918c8f562a2.camel@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=mnabipoor@gnu.org \
--cc=poke-devel@gnu.org \
/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).