From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id C5B1A3857C47 for ; Mon, 17 Aug 2020 12:21:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C5B1A3857C47 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark@simark.ca Received: from [10.0.0.11] (173-246-6-90.qc.cable.ebox.net [173.246.6.90]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 08BDA1E599; Mon, 17 Aug 2020 08:21:41 -0400 (EDT) Subject: Re: [PATCH] gdb: fix IA64 build failure of linux-nat To: Tom de Vries , Sergei Trofimovich , Kevin Buettner Cc: gdb-patches@sourceware.org, Sergei Trofimovich References: <20200519212710.1417100-1-slyfox@gentoo.org> <20200519150041.13df2b38@f31-4.lan> <20200816094521.061554bb@sf> <5f684182-c8d5-744b-8486-18f89ffb30a3@suse.de> From: Simon Marchi Message-ID: Date: Mon, 17 Aug 2020 04:21:40 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <5f684182-c8d5-744b-8486-18f89ffb30a3@suse.de> Content-Type: text/plain; charset=windows-1252 Content-Language: fr Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, DATE_IN_PAST_03_06, KAM_DMARC_STATUS, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2020 12:21:43 -0000 On 2020-08-17 4:54 a.m., Tom de Vries wrote: > Hi, > > IA64 support was just obsoleted in bfd (commit 73d0dc162e "Obsolete ia64"). > > So, AFAIU, this should now be built with --enable-obsolete. > > What are the consequences for gdb IA64 patches ? > > Thanks, > - Tom By transitivity, I'd say that the GDB port is also obsolete. But as long as it's in the tree, it's fine to accept patches to keep it building (otherwise it's useless to keep it in the tree). If you wanted to build GDB with --target=ia64-something-something, you'll need to pass --enable-obsolete in order to build BFD, which is a required dependency of GDB. When we pass --enable-targets=all, it builds a GDB with ia64 support without requiring that --enable-obsolete flag though. Do you know what's the BFD policy for obsolete configurations? If they wanted to get rid of it completely, they would need to remove GDB support too, otherwise they'd break the build. So should we eventually take the lead and remove support for it first? Sergei, quick survey: do you, or someone you know actually use GDB on ia64? Or you just noticed it not building because you package it? Simon