From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115653 invoked by alias); 17 Feb 2020 14:29:35 -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 115593 invoked by uid 89); 17 Feb 2020 14:29:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=our X-HELO: mail-qv1-f66.google.com Received: from mail-qv1-f66.google.com (HELO mail-qv1-f66.google.com) (209.85.219.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 17 Feb 2020 14:29:32 +0000 Received: by mail-qv1-f66.google.com with SMTP id y8so7648929qvk.6 for ; Mon, 17 Feb 2020 06:29:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=e6MSIvcogmZCr43x/8Tmv2RGNY0O1Kb4PVhWzpVzbYA=; b=BCcLcU6XpodCpMEWmjaDYrmZwAvo6vkUufr/zZgt18db8iWWb67nRod6+eUaYKoJnn H0Vd+TjiTECMzVT/+3df6TQon72KYc3mEjqSOEYpJRiTiLJ5nw7+U94h4P/l3iYU0dwI JPv/g/nDyUIWLvs6+HJ3cAKx4o+LredCkv4EpBoiaeovqATarjTz/qBHRamCMFEsiC1N 7xsLROmjcdL4j7rAtgmuRXs387U52kZWIni9sN0cO3tCOVtyvoxdbFsZ/SVYvAW9CoAy ed+uWnD8XOra6wTvM41STAUajkhHwRS88Zi06xs7mYm02qEyQeh186SNPIxP9ieq/PkY sOmw== Return-Path: Received: from [192.168.0.185] ([191.34.156.101]) by smtp.gmail.com with ESMTPSA id v125sm295657qkb.52.2020.02.17.06.29.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 Feb 2020 06:29:29 -0800 (PST) Subject: Re: [PATCH] Move gdbserver to top level To: "Maciej W. Rozycki" Cc: Tom Tromey , Sergio Durigan Junior , Tom de Vries , Pedro Alves , gdb-patches@sourceware.org References: <87d0bf45up.fsf@tromey.com> <7ceebbb7-b2f7-3d4a-1d8a-f31310badbe8@redhat.com> <874kwk8nz9.fsf@tromey.com> <171a3144-af37-1c29-a2a4-c4cd7eaa14c0@redhat.com> <87r1zm6x8s.fsf@tromey.com> <01b4b5ca-a802-54b5-3135-428b7c9faa84@redhat.com> <87o8uo4mj0.fsf@tromey.com> <87blqfn0d6.fsf@tromey.com> <0b6b4f24-f5c8-b236-c249-737e70395667@suse.de> <4d5a1276-91aa-7197-5f90-854767987f73@suse.de> <87imkeh1za.fsf@redhat.com> <87eev0bp4s.fsf@tromey.com> <8736bd3jt2.fsf@redhat.com> <8736bdj9qt.fsf@tromey.com> <87pnegan2x.fsf@tromey.com> From: Luis Machado Message-ID: <95b5bb43-aa02-0dfd-76ec-c7da9e85a758@linaro.org> Date: Mon, 17 Feb 2020 14:29: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; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00618.txt.bz2 On 2/17/20 11:21 AM, Maciej W. Rozycki wrote: > On Mon, 17 Feb 2020, Luis Machado wrote: > >> Should --disable-gdb also imply --disable-gdbserver? Or should we be >> able to build gdbserver without building gdb (sounds a bit more complex)? > > Nope, `--disable-gdb --enable-gdbserver' is typical for a cross-debug > environment, where you want to configure and build cross-GDB with > `--host=foo --target=bar' and `gdbserver' with `--host=bar'. Sometimes > your build environment may not even be capable to build native GDB with > `--host=bar', or your target system to run it, and in any case building > GDB takes a lot of processing time compared to `gdbserver'. So it would > be a waste of resources if we forced people to do that. Well, that is a fair point. In which case i think we have a bug in our hands. > > I build `gdbserver' by itself routinely, although I only did the minimum > to convert from the old layout, that is rather than calling `configure' > from gdb/gdbserver/ I now call it from gdbserver/. So far it has worked, > although with the new arrangement it probably qualifies as a hack, and may > stop working sometime. > > Maciej >