From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (elastic.org [96.126.110.187]) by sourceware.org (Postfix) with ESMTPS id 18D353858D28; Mon, 25 Apr 2022 10:43:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 18D353858D28 Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1niwBP-0005V6-5Z; Mon, 25 Apr 2022 10:43:07 +0000 Received: from fche by elastic.org with local (Exim 4.94.2) (envelope-from ) id 1niwBO-000QjS-Ku; Mon, 25 Apr 2022 06:43:06 -0400 Date: Mon, 25 Apr 2022 06:43:06 -0400 From: "Frank Ch. Eigler" To: Overseers mailing list Cc: Mark Wielaard , binutils@sourceware.org, "gdb@sourceware.org" , Luis Machado Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-100.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP, USER_IN_WELCOMELIST, USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2022 10:43:09 -0000 Hi - > As a general comment, I think we should have a single buildbot entry for the > whole of binutils-gdb. Perhaps! > Given changes to bfd and opcodes can affect gdb, why not build gdb alongside > the other tools? You don't need to run the gdb testsuite, which should make > things much more deterministic. But this is not an argument for building gdb as a part of testing binutils. This is an argument for building & testing gdb if binutils changes. That is: an additional buildbot job. - FChE