From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 669 invoked by alias); 15 Jan 2020 14:56:10 -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 561 invoked by uid 89); 15 Jan 2020 14:56:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy= X-HELO: us-smtp-1.mimecast.com Received: from us-smtp-delivery-1.mimecast.com (HELO us-smtp-1.mimecast.com) (205.139.110.120) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 15 Jan 2020 14:56:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579100158; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ifxopCwB6cTDSDU9fNTJu9v5EW6EtGrgYl1mkgP3zIY=; b=hvJJ5zKx2yzWhZSoVrmg1UImq+uIUlNFxqKMQ++tgS0HmngfxG5Ca1FGiwMO7k5LdxnCU+ k7T85yYR/nj9BAA+QhH0FG7xJ0qCO1iieO/ZBE9UxOLIVrtlqkaeF2wdoKZ6Ej6NTVXIMb k4g5kYBTfX+RYWstMv5+6Fgxkcrl3Do= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-258-wE0HPB1jMciHafu5vQ1G9w-1; Wed, 15 Jan 2020 09:55:57 -0500 Received: by mail-ed1-f72.google.com with SMTP id n63so11599610edc.20 for ; Wed, 15 Jan 2020 06:55:56 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f913:f700:56ee:75ff:fe8d:232b? ([2001:8a0:f913:f700:56ee:75ff:fe8d:232b]) by smtp.gmail.com with ESMTPSA id b4sm692489ejb.37.2020.01.15.06.55.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Jan 2020 06:55:54 -0800 (PST) Subject: Re: [PATCH v2 0/6] Move gdbsupport to top level From: Pedro Alves To: Tom Tromey , gdb-patches@sourceware.org References: <20200109005807.7314-1-tom@tromey.com> <8a8de6a9-37b8-cad3-c818-be903037fe48@redhat.com> Message-ID: <437c1b86-0aa8-57b9-53e2-f21567e2bb14@redhat.com> Date: Wed, 15 Jan 2020 16:07:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <8a8de6a9-37b8-cad3-c818-be903037fe48@redhat.com> X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-01/txt/msg00421.txt.bz2 On 1/15/20 2:41 PM, Pedro Alves wrote: > Don't know what I think of gnulib headers including . > Maybe we should rename gdb's config.h to gdb-config.h too. Hit reply to soon. I meant to add, ... and then, add a manually-written config.h in the build dir that does: #include #include We'd do the same to gdbsupport, add a config.h in its build dir that does: #include "gnulib/config.h" #include Those config.h files would go in the build dirs so that they're not picked by other build directories. With that, any "#include " in any header ends up picking the currently-being-built project's config.h, plus the dependencies' config.h files. Just a half-baked thought. Not sure it's the best idea. Thanks, Pedro Alves