From: Mark Wielaard <mark@klomp.org>
To: Luis Machado <luis.machado@arm.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Overseers mailing list <overseers@sourceware.org>,
binutils@sourceware.org
Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware
Date: Thu, 28 Apr 2022 16:48:34 +0200 [thread overview]
Message-ID: <20220428144834.GC23335@gnu.wildebeest.org> (raw)
In-Reply-To: <2878cbcf-86dd-ea34-15a7-38d4b8ba0136@arm.com>
Hi Luis,
On Thu, Apr 28, 2022 at 02:53:33PM +0100, Luis Machado wrote:
> On 4/28/22 14:50, Frank Ch. Eigler wrote:
> >(That's everything in binutils-gdb.git except binutils, cpu, gas,
> >gnulib, gold, gprof, gprofng, ld, texinfo.)
>
> Right. And now that you mentioned, I think gnulib as well. But most
> of these rarely change. do you think that is a bit too much?
Added gnulib. I think it is important to do a quick build for any
change in files that might cause build issues with gdb/gdbserver.
BTW the newly added gdb-fedora-s390x builder showed a compile issue:
https://builder.sourceware.org/buildbot/#builders/gdb-fedora-s390x But
my c++ warning message reading foo is not strong enough to understand
what it is saying (or why it is not an issue for the other builders)
It didn't sent email yet because it isn't a new failure.
Cheers,
Mark
next prev parent reply other threads:[~2022-04-28 14:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YmZkKRO+yUHeFqV0@wildebeest.org>
2022-04-25 10:37 ` Luis Machado via Gdb
2022-04-25 10:43 ` Frank Ch. Eigler via Gdb
2022-04-25 12:16 ` Luis Machado via Gdb
2022-04-25 12:30 ` Frank Ch. Eigler via Gdb
2022-04-25 18:20 ` Mark Wielaard
2022-04-25 18:27 ` Frank Ch. Eigler via Gdb
2022-04-25 22:11 ` Mark Wielaard
2022-04-26 3:33 ` Alan Modra via Gdb
2022-04-26 6:22 ` Jan Beulich via Gdb
2022-04-26 12:27 ` Nick Clifton via Gdb
2022-04-26 13:49 ` Jan Beulich via Gdb
2022-04-26 15:47 ` H.J. Lu via Gdb
2022-04-27 6:15 ` Jan Beulich via Gdb
2022-04-28 12:10 ` Nick Clifton via Gdb
2022-04-28 13:07 ` Jan Beulich via Gdb
2022-04-26 15:54 ` H.J. Lu via Gdb
2022-04-26 23:33 ` Alan Modra via Gdb
2022-04-27 18:32 ` [PATCH] x86: Disable 2 tests with large memory requirement H.J. Lu via Gdb
2022-04-26 7:01 ` Adding binutils to the GNU Toolchain buildbot on sourceware Luis Machado via Gdb
2022-04-26 9:40 ` Frank Ch. Eigler via Gdb
2022-04-26 22:59 ` Mark Wielaard
2022-04-26 22:34 ` Mark Wielaard
2022-04-28 12:23 ` Luis Machado via Gdb
2022-04-28 13:50 ` Frank Ch. Eigler via Gdb
2022-04-28 13:53 ` Luis Machado via Gdb
2022-04-28 14:22 ` Frank Ch. Eigler via Gdb
2022-04-28 17:04 ` Mark Wielaard
2022-04-28 14:48 ` Mark Wielaard [this message]
2022-04-28 14:19 ` Mark Wielaard
2022-04-28 14:47 ` Thomas Fitzsimmons
2022-04-28 16:28 ` Mark Wielaard
2022-04-29 20:04 ` gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Mark Wielaard
2022-05-01 19:44 ` Mark Wielaard
2022-05-03 15:41 ` Simon Marchi via Gdb
2022-05-13 8:21 ` Mark Wielaard
2022-04-28 17:50 ` Adding binutils to the GNU Toolchain buildbot on sourceware Nick Alcock via Gdb
2022-04-29 17:54 ` Mark Wielaard
2022-04-30 0:12 ` Nick Alcock via Gdb
2022-04-30 22:27 ` Mark Wielaard
2022-05-03 12:48 ` Nick Alcock via Gdb
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=20220428144834.GC23335@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.com \
--cc=overseers@sourceware.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