diff options
| author | Peter Collingbourne <peter@pcc.me.uk> | 2025-06-22 21:00:56 -0700 |
|---|---|---|
| committer | Bjørn Forsman <bjorn.forsman@gmail.com> | 2025-06-23 23:05:25 +0200 |
| commit | bfefc8d2f32a4f9d60da1cec33f67d2957a42f6d (patch) | |
| tree | 0af73ef3c0d1fd5b59636bf1219a9e855e06541d /pkgs/development/python-modules/rangehttpserver | |
| parent | f508b77c8f493b5f231d7c3e253e8abad19642b4 (diff) | |
gnat-bootstrap: remove ld binaries
After #400734 the path to the binutils wrapper is no longer passed via
-B and is instead passed via $PATH. This had the following consequences
for gnat-bootstrap:
- GCC appends $prefix/$triple/bin to collect2's $COMPILER_PATH, which
is where gnat-bootstrap's bundled linker binary is installed. For
normal gcc packages, this has no impact on linker selection because
binutils and gcc are installed to separate prefixes.
- -B paths are also added to $COMPILER_PATH but they appear before
$prefix/$triple/bin. This meant that gnat-bootstrap's collect2 would
find the binutils wrapper before #400734.
- collect2 searches for the linker on $PATH but only after failing to
find it on $COMPILER_PATH. Because #400734 caused the binutils wrapper
path to be removed from $COMPILER_PATH while the bundled linker on
$prefix/$triple/bin was still present, gnat-bootstrap started finding
the bundled linker on $COMPILER_PATH after #400734.
The bundled ld binaries should not be used by builds utilizing
gnat-bootstrap because we need our binutils wrappers to be used so that
RPATH is set correctly. The ld binaries are unused as far as I'm aware,
so remove them from the package so that collect2 finds the binutils
wrapper on $PATH.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
