From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111243 invoked by alias); 24 Feb 2020 19:46:31 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 111233 invoked by uid 89); 24 Feb 2020 19:46:30 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: simark.ca Received: from simark.ca (HELO simark.ca) (158.69.221.121) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 24 Feb 2020 19:46:29 +0000 Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (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 3A6CD1E5FA; Mon, 24 Feb 2020 14:46:28 -0500 (EST) Subject: Re: [PATCH] Change gdbserver to use existing gnulib and libiberty To: Tamar Christina , Tom Tromey , "gdb-patches@sourceware.org" Cc: nd References: <20200207225313.31092-1-tom@tromey.com> From: Simon Marchi Message-ID: <5f45f667-f425-d4e3-d0fd-3ed18c1dc590@simark.ca> Date: Mon, 24 Feb 2020 19:46:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-02/txt/msg00929.txt.bz2 On 2020-02-24 9:16 a.m., Tamar Christina wrote: > Hi Tom, > > We're having trouble building cross toolchains after this change. > > Before this we were able to build gdb running on HOST but build gdbserver running on TARGET. > > After this change we can no longer do this since you can't link objects from different architectures. > > Is this not a supported workflow anymore? Any suggestions how to do this after these changes? > > Thanks, > Tamar Hi Tamar, When you were building gdb running on HOST and gdbserver running on TARGET, I presume you were running two configure scripts, like this? $ .../binutils-gdb/configure --host=x86-foo --target=arm-bar and in another directory $ .../binutils-gdb/gdb/gdbserver/configure --host=arm-bar Now, gdbserver being a proper top-level project (just like gdb and binutils are), you can do: $ .../binutils-gdb/configure --host=x86-foo --target=arm-bar ... to configure GDB, and: $ .../binutils-gdb/configure --target=arm-bar ... to configure GDBserver. In fact, these commands set up build directories to build the entire binutils-gdb repository. You could either pass a bunch of --disable-* options to configure in order to disable the projects you don't want to build, or build using "make all-gdb" / "make all-gdbserver" to only build gdb or gdbserver respectively. Hope that helps. Simon