From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67844 invoked by alias); 2 May 2017 21:30:57 -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 67830 invoked by uid 89); 2 May 2017 21:30:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy=browse, Those, they're, theyre X-HELO: mail-wr0-f170.google.com Received: from mail-wr0-f170.google.com (HELO mail-wr0-f170.google.com) (209.85.128.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 02 May 2017 21:30:55 +0000 Received: by mail-wr0-f170.google.com with SMTP id w50so91942894wrc.0 for ; Tue, 02 May 2017 14:30:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=eodyiosqFZVyT3P46oR0XMikQXp6d6Ya4oonqvLQt2o=; b=Wzzl0hFH7ZABlmyNubIhnUGtidzFguM0pKn/FbNr3xq9jzVLasN3VomUksRS5DeBzd snlp3I6fssg68fm6OP25ncEVs/hFBJwJ2fTrqGXtwJKmmlpG74hvnUSxF1jOEAreTHN2 Xkwt+tQxgGp93ykagdOrP+1sbIkSISQB42i5hoqYWYG9vA7iEdUPvrwQJeyPaEcECNi/ pMzORRa0VB0WhtykAY86jIF5dhpAhLxUuAL715pkRNZBVzaimUQ3EczeRfq5xRu4LFxI 3SBObmGv8Fy9uvL1hic+jJjzYXi4rM6P1LEhPXo9kxHn5jer3tgu7t8DDETgmYzyJKk9 qTcQ== X-Gm-Message-State: AN3rC/7OK6KumKsqnvLcMf+imuS0xeit5IT7QPkA7mZIIZxSyWaSbQGc 9O88IPm+nUVEb4O7 X-Received: by 10.223.134.22 with SMTP id 22mr9893194wrv.182.1493760655485; Tue, 02 May 2017 14:30:55 -0700 (PDT) Received: from [192.168.0.102] ([37.189.166.198]) by smtp.gmail.com with ESMTPSA id r29sm16386240wrc.25.2017.05.02.14.30.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 May 2017 14:30:54 -0700 (PDT) Subject: Re: [PATCH] Introduce "gdb/configure.nat" (and delete "gdb/config/*/*.mh" files) To: Simon Marchi , Sergio Durigan Junior References: <20170425202309.15771-1-sergiodj@redhat.com> <8737cngise.fsf@redhat.com> Cc: GDB Patches , John Baldwin From: Pedro Alves Message-ID: <9a50363a-dfdf-de64-572c-49b0838c896b@redhat.com> Date: Tue, 02 May 2017 21:30:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-05/txt/msg00030.txt.bz2 Let's try to avoid mixing terminology here -- the NAT_ variables should not be described in terms of "host", but instead in terms of "native target". That's why they're called NAT_*. Host-dependent variables would be better (at some point, not in this particular patch) moved/left to configure.host instead. Those are supposedly bits that are necessary even if the native target backend is not included in the build. If the native target backends of gdb and gdbserver were already fully shared, then configure.nat would be shared, while gdb/configure.host would not. See also: https://sourceware.org/gdb/wiki/Internals%20Adding-a-New-Host https://sourceware.org/gdb/wiki/Internals%20Native-Debugging (/me mutters something about wikified internals manual being hard to search and browse.) Thanks, Pedro Alves