Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2F838C07548 for ; Thu, 10 Sep 2020 13:52:02 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id ACAB420809 for ; Thu, 10 Sep 2020 13:52:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=citrix.com header.i=@citrix.com header.b="Mu3Ng+NZ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org ACAB420809 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=citrix.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kGMzP-0000Mb-19; Thu, 10 Sep 2020 13:51:51 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kGMzO-0000MN-5p for xen-devel@lists.xenproject.org; Thu, 10 Sep 2020 13:51:50 +0000 X-Inumbo-ID: 248df837-ddfb-4dbf-8672-756bca2f8c4a Received: from esa3.hc3370-68.iphmx.com (unknown [216.71.145.155]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 248df837-ddfb-4dbf-8672-756bca2f8c4a; Thu, 10 Sep 2020 13:51:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=citrix.com; s=securemail; t=1599745909; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=TxJJJc8ne9kYw9e05f9qiHVYMUo1EuX2fTiABEUEDPg=; b=Mu3Ng+NZQTFH3SrUV3wvJwsvdjNqLr/wO8bMI3QyiIer6ZiYREFqqzGC h2utyaRSlpvn55mWrgBwVTLLbq9PexYfV4sxpdk2mQwHLW29+4d6eQHab 8Ryx6VQ8Khpe44bSygpWXBmldqhs17vid663xbJeekNrvG0N5UpTxvB8t 8=; Authentication-Results: esa3.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none IronPort-SDR: 4GyIGLCF4JhovU3x5A2/xZLTMC8bxHJNsb+lRoxTzSJXX+qpw6TFGpXSwFNtjCIrQMTBvDxFJb osZJcVsC3Z+mlmEJ0UIDRzCAu0LnJ9sZDiPZgsovA5asF/Q36F3acLFYDs6drNU4rvJy0tZ2oE R6zjnpoDKgkOVNliCaTQbozTGjKbmwRUZUzp1/c4TJa6q+6Bxd8YjdYmkxDXIdjyBhoW1FuHH0 v+ViIC9lKIjRGwt2KGc/LqyICUi8QiYIwJwv2Mn/Gi3L2pQPmLNW3rJ4/xDq+uID7taJvABdK+ qbk= X-SBRS: 2.7 X-MesageID: 26384783 X-Ironport-Server: esa3.hc3370-68.iphmx.com X-Remote-IP: 162.221.158.21 X-Policy: $RELAYED X-IronPort-AV: E=Sophos;i="5.76,413,1592884800"; d="scan'208";a="26384783" Subject: Re: [PATCH 0/6] tools/include: adjustments to the population of xen/ To: Jan Beulich , "xen-devel@lists.xenproject.org" CC: Ian Jackson , Wei Liu References: <2a9f86aa-9104-8a45-cd21-72acd693f924@suse.com> From: Andrew Cooper Message-ID: <2d5579e4-74cf-fd35-da7d-a8f4de2c2c86@citrix.com> Date: Thu, 10 Sep 2020 14:51:43 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <2a9f86aa-9104-8a45-cd21-72acd693f924@suse.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Language: en-GB X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To FTLPEX02CL05.citrite.net (10.13.108.178) X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" On 10/09/2020 13:09, Jan Beulich wrote: > While looking at what it would take to move around libelf/ > in the hypervisor subtree, I've run into this rule, which I > think can do with a few improvements and some simplification. I realise this might be a controversial move, but can we *please* address this by removing our use of symlinking, rather than kicking the problem down the road. For header files in particular, there is no need to symlink at all.  Some properly formed -I runes for the compiler will do the right thing, and avoid all intermediate regeneration issues. ~Andrew