From: Patrick Steinhardt <ps@pks.im>
To: Justin Tobler <jltobler@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 01/11] meson: fix exec path with enabled runtime prefix
Date: Thu, 30 Jan 2025 08:06:10 +0100 [thread overview]
Message-ID: <Z5sk4iIDTHDG3Gi_@pks.im> (raw)
In-Reply-To: <7rnnfxsi4taxtyqek5udyplp767w6jdbw3zshvbbsbc5qxmjs6@ftjofkjsnzyb>
On Wed, Jan 29, 2025 at 02:12:35PM -0600, Justin Tobler wrote:
> On 25/01/29 08:11AM, Patrick Steinhardt wrote:
> > When the runtime prefix option is enabled, Git is built such that it
> > knows to locate its binaries relative to the directory a binary is being
> > executed from. This requires us to figure out relative paths, which is
> > handled in `system_prefix()` by trying to strip a couple of well-known
> > paths.
>
> Ok if I understand this correctly, when the runtime prefix option is
> enabled, the prefix that gets setup by `system_prefix()` is expected to
> be relative from the directory the binary is being executed at.
>
> > One of these paths, GIT_EXEC_PATH, is expected to be absolute when
> > runtime prefixes are enabled, but relative otherwise. And while our
> > Makefile gets this correcty, in Meson we always wire up the absolute
>
> s/correcty/correctly/
>
> > path, which may result in us not being able to find binaries.
>
> So the problem is that since GIT_EXEC_PATH is always defined as
> absolute, when the runtime prefix option is enabled, the relative prefix
> is not able to be correctly set and thus always uses the
> `FALLBACK_RUNTIME_PREFIX`.
Yup, excatly.
Patrick
next prev parent reply other threads:[~2025-01-30 7:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 7:11 [PATCH 00/11] meson: cleanups, improvements, smallish fixes Patrick Steinhardt
2025-01-29 7:11 ` [PATCH 01/11] meson: fix exec path with enabled runtime prefix Patrick Steinhardt
2025-01-29 20:12 ` Justin Tobler
2025-01-30 7:06 ` Patrick Steinhardt [this message]
2025-01-29 7:11 ` [PATCH 02/11] meson: inline the static 'git' library Patrick Steinhardt
2025-01-29 7:11 ` [PATCH 03/11] meson: simplify use of the common-main library Patrick Steinhardt
2025-01-29 7:11 ` [PATCH 04/11] meson: stop linking libcurl into all executables Patrick Steinhardt
2025-01-29 7:11 ` [PATCH 05/11] meson: introduce `libgit_curl` dependency Patrick Steinhardt
2025-01-29 7:11 ` [PATCH 06/11] meson: drop separate version library Patrick Steinhardt
2025-01-29 7:12 ` [PATCH 07/11] meson: deduplicate the list of required programs Patrick Steinhardt
2025-01-29 20:28 ` Justin Tobler
2025-01-29 7:12 ` [PATCH 08/11] meson: simplify setup of PATH environment variable Patrick Steinhardt
2025-01-29 20:42 ` Justin Tobler
2025-01-30 7:06 ` Patrick Steinhardt
2025-01-29 7:12 ` [PATCH 09/11] meson: prevent finding sed(1) in a loop Patrick Steinhardt
2025-01-29 7:12 ` [PATCH 10/11] meson: fix overwritten `git` variable Patrick Steinhardt
2025-01-29 7:12 ` [PATCH 11/11] meson: consistently use custom program paths to resolve programs Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 00/13] meson: cleanups, improvements, smallish fixes Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 01/13] meson: fix exec path with enabled runtime prefix Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 02/13] meson: fix OpenSSL fallback when not explicitly required Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 03/13] meson: inline the static 'git' library Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 04/13] meson: simplify use of the common-main library Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 05/13] meson: introduce `libgit_curl` dependency Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 06/13] meson: stop linking libcurl into all executables Patrick Steinhardt
2025-01-30 14:43 ` [PATCH v2 07/13] meson: drop separate version library Patrick Steinhardt
2025-02-07 13:24 ` Toon Claes
2025-01-30 14:44 ` [PATCH v2 08/13] meson: improve PATH handling Patrick Steinhardt
2025-01-30 14:44 ` [PATCH v2 09/13] meson: improve handling of `sane_tool_path` option Patrick Steinhardt
2025-02-07 13:49 ` Toon Claes
2025-02-07 14:29 ` Patrick Steinhardt
2025-01-30 14:44 ` [PATCH v2 10/13] meson: prevent finding sed(1) in a loop Patrick Steinhardt
2025-01-30 14:44 ` [PATCH v2 11/13] meson: fix overwritten `git` variable Patrick Steinhardt
2025-01-30 14:44 ` [PATCH v2 12/13] meson: consistently use custom program paths to resolve programs Patrick Steinhardt
2025-01-30 14:44 ` [PATCH v2 13/13] gitlab-ci: restrict maximum number of link jobs on Windows Patrick Steinhardt
2025-02-07 15:22 ` [PATCH v2 00/13] meson: cleanups, improvements, smallish fixes Justin Tobler
2025-02-26 8:22 ` [PATCH v3 " Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 01/13] meson: fix exec path with enabled runtime prefix Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 02/13] meson: fix OpenSSL fallback when not explicitly required Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 03/13] meson: inline the static 'git' library Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 04/13] meson: simplify use of the common-main library Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 05/13] meson: introduce `libgit_curl` dependency Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 06/13] meson: stop linking libcurl into all executables Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 07/13] meson: drop separate version library Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 08/13] meson: improve PATH handling Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 09/13] meson: improve handling of `sane_tool_path` option Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 10/13] meson: prevent finding sed(1) in a loop Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 11/13] meson: fix overwritten `git` variable Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 12/13] meson: consistently use custom program paths to resolve programs Patrick Steinhardt
2025-02-26 8:22 ` [PATCH v3 13/13] gitlab-ci: restrict maximum number of link jobs on Windows Patrick Steinhardt
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=Z5sk4iIDTHDG3Gi_@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=jltobler@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.