From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.axis.com (smtp1.axis.com [195.60.68.17]) by sourceware.org (Postfix) with ESMTPS id 5D84A3858C74 for ; Tue, 21 Jun 2022 19:06:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5D84A3858C74 From: Hans-Peter Nilsson To: Nick Alcock CC: , , In-Reply-To: <874k0dsy18.fsf@esperi.org.uk> (message from Nick Alcock on Tue, 21 Jun 2022 19:53:55 +0200) Subject: Re: Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT References: <20220621103204.1C6EB3870847@sourceware.org> <20220621170134.8F75120427@pchp3.se.axis.com> <874k0dsy18.fsf@esperi.org.uk> Message-ID: <20220621190607.43E3220417@pchp3.se.axis.com> Date: Tue, 21 Jun 2022 21:06:07 +0200 X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2022 19:06:14 -0000 > From: Nick Alcock > Date: Tue, 21 Jun 2022 19:53:55 +0200 > >> make[1]: Entering directory '/opt/local/build/binutils-gdb-obj/ld' > >> Makefile:2629: .deps/emmo.Pc: No such file or directory > >> make[1]: *** No rule to make target '.deps/emmo.Pc'. Stop. > [...] > > I had the same confusion when I had a (brief) look into my > > own autobuilder failure and made a feeble attempt at > > tracking it down. Maybe a bug in automake-1.16... > > It's pretty clear that this is just another case of regenerating with > the wrong tools. There are changes in the generated configure.ac that I > would not expect from those source changes, and regenerating with > upstream autoconf 2.69 produces a build that works again. So the > ld/configure in that commit was generated with some (distro-patched) > Autoconf by mistake. Well obviously and thanks for fixing it; I don't have my keys here or I'd done the same. The behavior was IMHO interesting nevertheless. It looks like the .deps directory wasn't created, whether due to the mixup or an automake change is still unknown. The behavior is IMHO unexpected as ./$(DEPDIR)/emmo.Pc is the *last* included file in ld/Makefile, but a quick experiment shows that this is indeed a GNU make quirk: the error message has the last, not the first included file, that's missing. brgds, H-P