From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id hGvuHikf2mU0NysAWB0awg (envelope-from ) for ; Sat, 24 Feb 2024 11:54:01 -0500 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=M3EsYX/K; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 6739E1E0D2; Sat, 24 Feb 2024 11:54:01 -0500 (EST) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 484AD1E030 for ; Sat, 24 Feb 2024 11:53:59 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id AAED33858281 for ; Sat, 24 Feb 2024 16:53:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AAED33858281 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1708793638; bh=s/j8yfKBqWBoL+ElRxOiuHfnNC2sG6Q5e1c3tUjTcu0=; h=References:To:Cc:Subject:Date:In-reply-to:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=M3EsYX/K86YuWZKyghdEehmy5BvuSvQWvBgVcRQ6dWcEgcqsbjUH7p5h95FvBmh5Z WTmu1tG8dZSo5WC6YlZdl1jQfnCtN7d9lL85xKgvrpsDrt5tChjmq5YlUHXhY3z+r7 Vuaad5sX3yD8C7p6y79jRQYQu1YjDR1rXynXzz1k= Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) by sourceware.org (Postfix) with ESMTP id 9A4443858D1E for ; Sat, 24 Feb 2024 16:53:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9A4443858D1E ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 9A4443858D1E ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708793602; cv=none; b=h9+WAhYMEvtD+oYoH7RawlIhmgyip3Tq/dlD5NGf+oHvZW5rEwbiwFv7/60yytuJ8+Pcp6R9woRa51xpkXN+Mf68rleKOg1KkcUgsY22Lt3kYIagJP8sLbXMrDQvR5jp8ncSH7KsMtfjuBoXAYejvf2OwdOVp5qXHhcK6gS4De0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708793602; c=relaxed/simple; bh=s/j8yfKBqWBoL+ElRxOiuHfnNC2sG6Q5e1c3tUjTcu0=; h=From:To:Subject:Date:Message-ID:MIME-Version; b=o+yX4gGmD1hysy5ji3Ik8U4yVgcc9vaAPIayUXQOAy3Vjae9GKCWvIdcQUREzW1rgCDrSKEPH28wCAmcInp3X05uCiWV+/OHDrPmhtfNVMZxqc8yHXMjvdcPyZhD3kG0O+0PI/bi9e8VERs/5xHy2DyQZEo4iN/MkBcdh30Pzmg= ARC-Authentication-Results: i=1; server2.sourceware.org References: User-agent: mu4e 1.10.8; emacs 30.0.50 To: Tomasz =?utf-8?Q?K=C5=82oczko?= Cc: gdb@sourceware.org Subject: Re: gdb and ancient GNU autotools Date: Sat, 24 Feb 2024 16:51:04 +0000 Organization: Gentoo In-reply-to: Message-ID: <87v86d6byg.fsf@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, 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: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Sam James via Gdb Reply-To: Sam James Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Tomasz K=C5=82oczko via Gdb writes: > Hi, > > In gdb source tree in config/override.m4 is hardcoded autoconf version > > m4_if(m4_defn([m4_PACKAGE_VERSION]), [2.64], > > That version has been released almost SIXTEEN YEARS AGO !!! > https://savannah.gnu.org/news/?id=3D5867 That specific line is adding a workaround for a bug in GNU Autoconf 2.64. It does not require 2.64. However, yes, _GCC_AUTOCONF_VERSION is indeed later set to 2.69 and will bail if *that* version isn't used. It would be worth updating to autoconf-2.72 but it needs to be coordinated across binutils, gdb, and gcc. > > Literally NONE Linux distribution currently provides that version so in > case of any necessity to fix something in autoconf it is NOT POSSIBLE to > regenerate GNU autotools files. > This is wrong, per above. > The same situation is with binutils ang gcc. Yes, they share the toplevel build system.