public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Nathanael Nerode" <ncn_gcc10@fastmail.fm>
To: "FX Coudert" <fxcoudert@gmail.com>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>
Cc: "Joseph Myers" <joseph@codesourcery.com>,
	"bonzini@gnu.org" <bonzini@gnu.org>,
	neroden@gcc.gnu.org, aoliva@gcc.gnu.org, Ralf.Wildenhues@gmx.de,
	"Iain Sandoe" <iains.gcc@gmail.com>
Subject: Re: Darwin: Replace environment runpath with embedded [PR88590]
Date: Sun, 08 Oct 2023 09:07:28 -0400	[thread overview]
Message-ID: <129c7396-2aa4-4551-8e4c-291519f9b6ae@app.fastmail.com> (raw)
In-Reply-To: <D0278826-8331-440C-81A4-EABFF326575F@gmail.com>

I hope a global maintainer can step up.  I've been on hiatus from GCC work for some years, and this was never my part of the build system anyway -- and I don't use Darwin -- so I'm not qualified to review it.  It looks fine but it should be reviewed by someone who knows what they're doing.

On Wed, Sep 20, 2023, at 9:52 AM, FX Coudert wrote:
> ping**2 for a build maintainer or global maintainer to review, please
> It restores testing on darwin >= 21, which is not currently working
>
> If no maintainer is available to review build system, could I get 
> guidance on how to proceed further?
>
> Thanks,
> FX
>
>
>> Le 12 sept. 2023 à 19:52, FX Coudert <fxcoudert@gmail.com> a écrit :
>> 
>> Hi build maintainers,
>> 
>> May I ping this series of patches for review? In particular, they allow to restore testing on darwin, which is currently broken with darwin >= 21, due to DYLD_LIBRARY_PATH being systematically removed from the environment by system tools.
>> 
>> It has been tested for two years on darwin, and would allow to restore regular regtesting on that target. It is a big step to help prevent bugs being undetected on this port.
>> 
>> The patchset was okayed from the driver point of view, but we need a build reviewer (or global reviewer) to okay those bits. Original presentation of the patches:
>> 
>> ------
>> I’d like to post an updated and rebased version of Iain Sandoe’s patches for modern darwin, originally posted in November 2021: https://gcc.gnu.org/pipermail/gcc-patches/2021-November/584775.html
>> 
>> The rationale in that message is pretty much unchanged, and the patches have been since tested thoroughly on darwin (both Intel and ARM) for almost two years now. We have been shipping Iain’s branch (including these patches) since then in Homebrew and most other major distros of GCC on Darwin. So I think it’s been very thoroughly tested.
>> 
>> The main comment that arose from review in the previous incarnation was the need to at least offer the libtool part of the patch to upstream, in order to reduce in the long term the divergence between our version and upstream. I have done so in https://savannah.gnu.org/patch/index.php?10385
>> 
>> (I would also note that I have offered other suggestions of small snippets that could be upstream in libtool for darwin, but have not received much feedback for now: https://savannah.gnu.org/patch/?10371)
>> ------
>> 
>> 
>> Thanks,
>> FX
>> 
>> 
>> 
>>> Le 29 août 2023 à 22:17, FX Coudert <fxcoudert@gmail.com> a écrit :
>>> 
>>>> I think a build machinery review is needed.
>>> 
>>> Thanks. CC’ing the relevant maintainers for review of the build part.
>>> The driver part and the darwin-specific part are already okayed.
>>> 
>>> FX
>
>
> Attachments:
> * 0001-Driver-Provide-a-spec-to-insert-rpaths-for-compiler-.patch
> * 0002-Darwin-Allow-for-configuring-Darwin-to-use-embedded-.patch
> * 0003-Darwin-rpaths-Add-with-darwin-extra-rpath.patch
> * 0004-Testsuite-allow-non-installed-testing-on-darwin.patch
> * 0005-Doc-document-the-new-Darwin-options.patch

  reply	other threads:[~2023-10-08 13:07 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 [this message]
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
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=129c7396-2aa4-4551-8e4c-291519f9b6ae@app.fastmail.com \
    --to=ncn_gcc10@fastmail.fm \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=aoliva@gcc.gnu.org \
    --cc=bonzini@gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    --cc=joseph@codesourcery.com \
    --cc=neroden@gcc.gnu.org \
    /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).