public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iains.gcc@gmail.com>
To: FX Coudert <fxcoudert@gmail.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	Martin Jambor <mjambor@suse.cz>
Subject: Re: Darwin: Replace environment runpath with embedded [PR88590]
Date: Wed, 22 Nov 2023 10:52:39 +0000	[thread overview]
Message-ID: <3D7BD6A2-6B28-4AF6-9194-F93B3C207571@gmail.com> (raw)
In-Reply-To: <92736664-0EF6-4A62-B309-31311B736892@gmail.com>

Hi FX,

> On 17 Nov 2023, at 14:20, FX Coudert <fxcoudert@gmail.com> wrote:
> 
>>> I have done a full rebuild, and having looked more at the structure of libtool.m4 I am now convinced that having that line outside of the scope of _LT_DARWIN_LINKER_FEATURES is simply wrong (probably a copy-pasto or leftover from earlier code).

The latter;  my original patch to do this had all the work inside libtool.m4 - but that proved to be unwieldy in practice, so
the eventual patch split the ENABLE_DARWIN_AT_RPATH AM_CONDITIONAL out and applies it (after libtool is
initiallised) in configure.ac cases that need it.

It seems I failed to remove all the old code in that change :(.

>>> Having rebuilt everything, it only manifests itself in fixincludes/ChangeLog. Iain is traveling right now, but when he is back I would like to submit this patch if he agrees with the above. It was regtested on x86_64-apple-darwin21.

I have also regtested on i686, x86_64, aarch64 Darwin, x86_64 and aarch64 Linux.
> 
> With the correct patch attached.

I believe this can be applied as a partial reversion of a previously approved patch,
thanks
Iain

> 
> <0001-Build-fix-error-in-fixinclude-configure.patch>


  reply	other threads:[~2023-11-22 10:52 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 16:58 FX Coudert
2023-08-18 20:17 ` Joseph Myers
2023-08-18 22:31   ` Iain Sandoe
2023-08-18 22:59     ` Joseph Myers
2023-08-18 23:05       ` Iain Sandoe
2023-08-25  7:50   ` FX Coudert
2023-08-25 16:28     ` Joseph Myers
2023-08-29 16:06       ` FX Coudert
2023-08-29 19:55         ` Joseph Myers
2023-08-29 20:17           ` FX Coudert
2023-09-12 17:52             ` FX Coudert
2023-09-20 13:52               ` FX Coudert
2023-10-08 13:07                 ` Nathanael Nerode
2023-10-08 22:14                   ` Iain Sandoe
2023-10-21 18:05                     ` Jeff Law
2023-10-21 18:26                       ` Iain Sandoe
2023-10-21  5:27             ` Alexandre Oliva
2023-10-22 21:18               ` FX Coudert
2023-11-30 19:43                 ` Ian Lance Taylor
2023-11-30 19:56                   ` Iain Sandoe
2023-11-30 19:58                     ` Ian Lance Taylor
2023-11-30 21:25                       ` Ian Lance Taylor
2023-10-30 16:17 ` Martin Jambor
     [not found] ` <653fd72a.050a0220.a6a20.de86SMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-30 16:19   ` Iain Sandoe
2023-10-30 16:31   ` FX Coudert
2023-10-30 19:08     ` Iain Sandoe
2023-11-15 20:11       ` Thomas Schwinge
2023-11-15 20:34         ` FX Coudert
2023-11-17 11:56           ` FX Coudert
2023-11-17 12:13             ` Thomas Schwinge
2023-11-17 14:20               ` FX Coudert
2023-11-22 10:52                 ` Iain Sandoe [this message]
2023-11-22 10:55                   ` FX Coudert
2023-11-13 15:27 ` gfortran.dg/dg.exp debug messages pollute test output Rainer Orth
2023-11-13 16:19   ` Iain Sandoe
2023-11-15 10:29     ` FX Coudert
2023-11-15 12:04       ` Rainer Orth
2023-11-17 12:36       ` Thomas Schwinge
2023-11-18  9:03         ` FX Coudert

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=3D7BD6A2-6B28-4AF6-9194-F93B3C207571@gmail.com \
    --to=iains.gcc@gmail.com \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    --cc=thomas@codesourcery.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).