From: Luis Machado <luis.machado@arm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>,
binutils@sourceware.org,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware
Date: Thu, 28 Apr 2022 13:23:44 +0100 [thread overview]
Message-ID: <16fe426d-c436-f030-dc43-0e81e7f0e853@arm.com> (raw)
In-Reply-To: <YmhzY4c3pOPLRgSw@wildebeest.org>
On 4/26/22 23:34, Mark Wielaard wrote:
> Hi Luis,
>
> On Tue, Apr 26, 2022 at 08:01:33AM +0100, Luis Machado wrote:
>>> If so lets just pick one or more of the workers which seem like stable
>>> distros/arches that should always build gdb:
>>> https://builder.sourceware.org/buildbot/#/workers
>>> (don't pick sourceware, which is special, debian-arm64, debian-armhf,
>>> debian-i386 or fedora-ppc64 which are too slow)
>>>
>>> Provide a file list (directories) of files in the binutils-gdb.git
>>> repo that should trigger a build.
>>>
>>> A configure and make line that does a quick build for just
>>> gdb/gdbserver which should always build.
>>
>> I think the following will do:
>>
>> ./configure --enable-targets=all; make all-gdb all-gdbserver
>>
>> or
>>
>> ./configure --enable-targets=all --disable-sim; make all-gdb all-gdbserver
>>
>> gdbserver, unlike gdb, will only build natively, hence why it would benefit
>> from being built everywhere.
>
> I added a gdb-centos-x86_64 builder. That is a fairly old distro (it
> is centos7) but the worker isn't used for that many other builds and
> it can do a quick compile in under 5 minutes. Once it works out I'll
> add some other distro/arches.
>
> Please review the gdb important files list. I might have missed some
> directoy.
>
> Thanks,
>
> Mark
It would make sense to build-test gdb if any of the following changes:
bfd/
config/
gdb/
gdbserver/
gdbsupport/
include/
intl/
libbacktrace/
libctf/
libdecnumber/
libiberty/
opcodes/
readline/
sim/
zlib/
next prev parent reply other threads:[~2022-04-28 12:24 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
2022-04-25 10:43 ` Frank Ch. Eigler
2022-04-25 12:16 ` Luis Machado
2022-04-25 12:30 ` Frank Ch. Eigler
2022-04-25 18:20 ` Mark Wielaard
2022-04-25 18:27 ` Frank Ch. Eigler
2022-04-25 22:11 ` Mark Wielaard
2022-04-26 3:33 ` Alan Modra
2022-04-26 6:22 ` Jan Beulich
2022-04-26 12:27 ` Nick Clifton
2022-04-26 13:49 ` Jan Beulich
2022-04-26 15:47 ` H.J. Lu
2022-04-27 6:15 ` Jan Beulich
2022-04-28 12:10 ` Nick Clifton
2022-04-28 13:07 ` Jan Beulich
2022-04-26 15:54 ` H.J. Lu
2022-04-26 23:33 ` Alan Modra
2022-04-27 18:32 ` [PATCH] x86: Disable 2 tests with large memory requirement H.J. Lu
2022-04-26 7:01 ` Adding binutils to the GNU Toolchain buildbot on sourceware Luis Machado
2022-04-26 9:40 ` Frank Ch. Eigler
2022-04-26 22:59 ` Mark Wielaard
2022-04-26 22:34 ` Mark Wielaard
2022-04-28 12:23 ` Luis Machado [this message]
2022-04-28 13:50 ` Frank Ch. Eigler
2022-04-28 13:53 ` Luis Machado
2022-04-28 14:22 ` Frank Ch. Eigler
2022-04-28 17:04 ` Mark Wielaard
2022-04-28 14:48 ` Mark Wielaard
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
2022-05-13 8:21 ` Mark Wielaard
2022-04-28 17:50 ` Adding binutils to the GNU Toolchain buildbot on sourceware Nick Alcock
2022-04-29 17:54 ` Mark Wielaard
2022-04-30 0:12 ` Nick Alcock
2022-04-30 22:27 ` Mark Wielaard
2022-05-03 12:48 ` Nick Alcock
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=16fe426d-c436-f030-dc43-0e81e7f0e853@arm.com \
--to=luis.machado@arm.com \
--cc=binutils@sourceware.org \
--cc=fche@elastic.org \
--cc=gdb@sourceware.org \
--cc=mark@klomp.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).