From: Joseph Myers <joseph@codesourcery.com>
To: FX Coudert <fxcoudert@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>, Iain Sandoe <iains.gcc@gmail.com>
Subject: Re: Darwin: Replace environment runpath with embedded [PR88590]
Date: Fri, 18 Aug 2023 20:17:19 +0000 [thread overview]
Message-ID: <92993a50-9667-45da-a62-5089e7e052f8@codesourcery.com> (raw)
In-Reply-To: <FA6935A5-6AC9-469C-969E-461E9151B5D3@gmail.com>
On Tue, 15 Aug 2023, FX Coudert via Gcc-patches wrote:
> I am currently retesting the patches on various archs (Linux and Darwin)
> after a final rebase, but various previous versions were
> regression-tested, and have been shipped for a long time in Homebrew.
>
> OK to commit?
The driver changes are OK.
I think the new configure options and the new -nodefaultrpaths compiler
option need documenting (I suppose there might be a case for the configure
option defined in libtool code being documented somewhere in libtool, if
there's somewhere appropriate, but I don't see that in the libtool patch
submission).
The help text for --enable-darwin-at-rpath refers to it as
--enable-darwin-at-path.
Somewhere the documentation ought to discuss the considerations around
embedding such paths in binaries, and what's appropriate for building a
binary on the system where it's going to be used, versus using the
compiler to build redistributed binaries that will be run on a system that
doesn't have the compiler installed (and so shouldn't have hardcoded paths
that were only applicable on the system with the compiler, but will need
to be able to find shared libraries - probably shipped with the binary -
somehow).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-08-18 20:17 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 [this message]
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
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=92993a50-9667-45da-a62-5089e7e052f8@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=fxcoudert@gmail.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).