From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from esa1.mentor.iphmx.com (esa1.mentor.iphmx.com [68.232.129.153]) by sourceware.org (Postfix) with ESMTPS id 6EABB3858422 for ; Thu, 18 Nov 2021 21:49:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6EABB3858422 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=codesourcery.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mentor.com IronPort-SDR: HzEs39893XF2QKOpuX7aB/5RREpDislsrNPRSbmqashRjaJId55gXbQM5vRSeOKUgzYhR6kl60 a7Odd2ALajhzrAJ0uAuGqH1XuZoTGuACoeuas14CcHicz+lYG7KrqIUUXlyBSyWguAaKr9M5wB 7HWnjp1lP6YLmgqrLJCFE5YPJxbF18H9zn7VKEQ3IaZJs5ZMB6ZpSyCKZVi5jUMitOdBsIATFY xZxgThkOVud1bFUan8tJzS8gLxCRUFEbArbHkQkhEy9lr4S2OYvtxkp40UwWT3+2+DIM2w+U8I NC547yqxBxf1VhVbWsCbnTF5 X-IronPort-AV: E=Sophos;i="5.87,245,1631606400"; d="scan'208";a="71160235" Received: from orw-gwy-01-in.mentorg.com ([192.94.38.165]) by esa1.mentor.iphmx.com with ESMTP; 18 Nov 2021 13:49:09 -0800 IronPort-SDR: NtP2VKp4Yg1pwp0HUnE6Y1aPgXMPXPeS5r0X0RdDjxtZNi8+kwW/r8PyAt4nHxKwxVRL0MhqRk fQLiL2C1Tcr/LoR/sEXID04X9CjToKAx+VZq0o+PtS1XAWCdAmUZH9hThgE0v5BY4hVn22yURd d8TcXeZqPs20eInhL52MunUCQCGUqfKfN+oOekrZfa9bkhAhw6LvaeDOLGnPAD6Qf/rJJ72bpU /CcwaiH4bNJH1xPoWklBxubEatzJCUJldhk96sP4l504cdtsIwWF3u11LilvLW2ByVBFJpcQSp NFo= Date: Thu, 18 Nov 2021 21:49:03 +0000 From: Joseph Myers X-X-Sender: jsm28@digraph.polyomino.org.uk To: Iain Sandoe CC: Subject: Re: [PATCH 3/4] Darwin : Allow for configuring Darwin to use embedded runpath. In-Reply-To: <5A0E60C6-5117-473A-8319-C12C90C3A92E@gmail.com> Message-ID: References: <20211117210319.92514-1-iain@sandoe.co.uk> <20211117210319.92514-2-iain@sandoe.co.uk> <20211117210319.92514-3-iain@sandoe.co.uk> <20211117210319.92514-4-iain@sandoe.co.uk> <5A0E60C6-5117-473A-8319-C12C90C3A92E@gmail.com> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: SVR-IES-MBX-04.mgc.mentorg.com (139.181.222.4) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-Spam-Status: No, score=-3116.8 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2021 21:49:13 -0000 On Wed, 17 Nov 2021, Iain Sandoe via Gcc-patches wrote: > If we are going to try and reconcile GCC’s local libtool for more > generic Darwin use, then I fear that is going to take quite significant > work over a period of time (since it will need much more wide testing > than GCC). The goal isn't any kind of merging GCC's libtool with upstream right now. But, once the new maintainer has got through the patch backlog, we'd like to be in a position where the starting point for a libtool update in GCC is simply taking upstream libtool and reverting libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c to deal with a mismatch of --with-sysroot interpretations - but not needing any local changes other than that reversion. If each local libtool patch gets submitted upstream before being applied to GCC, that reduces the chances of missing some significant local change that needs to be reapplied when updating libtool (given that GCC is apparently using libtool commit 2c9c38d8a12eb0a2ce7fe9c3862523026c3d5622 from 2009, it may well be nontrivial to figure out whether a given local change is actually relevant with a new libtool version or not). -- Joseph S. Myers joseph@codesourcery.com