public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Iain Sandoe <iains.gcc@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 3/4] Darwin : Allow for configuring Darwin to use embedded runpath.
Date: Thu, 18 Nov 2021 21:49:03 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2111182144400.1393807@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5A0E60C6-5117-473A-8319-C12C90C3A92E@gmail.com>

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

  reply	other threads:[~2021-11-18 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 21:03 [PATCH 0/4] Darwin: Replace environment runpath with embedded [PR88590] Iain Sandoe
2021-11-17 21:03 ` [PATCH 1/4] Driver : Provide a spec to insert rpaths for compiler lib dirs Iain Sandoe
2021-11-17 21:03   ` [PATCH 2/4] Darwin : Handle rpaths given on the command line Iain Sandoe
2021-11-17 21:03     ` [PATCH 3/4] Darwin : Allow for configuring Darwin to use embedded runpath Iain Sandoe
2021-11-17 21:03       ` [PATCH 4/4] Darwin, Ada : Add loader path as a default rpath Iain Sandoe
2021-11-18  7:28         ` Arnaud Charlet
2021-11-17 22:50       ` [PATCH 3/4] Darwin : Allow for configuring Darwin to use embedded runpath Joseph Myers
2021-11-17 23:30         ` Iain Sandoe
2021-11-18 21:49           ` Joseph Myers [this message]
     [not found]       ` <160318AE-E2F4-4612-AEC1-5013419B6359@gmail.com>
2021-11-18 15:34         ` Jonathan Wakely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2111182144400.1393807@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).