From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id qU6tHJJ7ZmLLcQIAWB0awg (envelope-from ) for ; Mon, 25 Apr 2022 06:44:34 -0400 Received: by simark.ca (Postfix, from userid 112) id 67A801E058; Mon, 25 Apr 2022 06:44:34 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=YqktCorS; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 09BFA1E01D for ; Mon, 25 Apr 2022 06:44:34 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 83AAC3858413 for ; Mon, 25 Apr 2022 10:44:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 83AAC3858413 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1650883473; bh=L2366lAJCT+J5YPG22Zbb91Cay0aP8VrWewDQJUyMnQ=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=YqktCorS5HwzAwtcpaBFRx0Er7kvPTSoNQM/G84F9rLcTVT02+uh1SKZVMN9dBUJw Bf8m3/OMaCY5OZAZq+m3+6z3hL7ABMxXoJstu1OFI616rKPDVsZzqoTF0vKiStDnBp JSGalHVIE9jB0UiBNiKsOTPNpQsBAQORBioO9bWU= 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 To: Overseers mailing list 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-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: , From: "Frank Ch. Eigler via Gdb" Reply-To: "Frank Ch. Eigler" Cc: "gdb@sourceware.org" , Mark Wielaard , binutils@sourceware.org Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" 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