summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorPeter Collingbourne <peter@pcc.me.uk>2025-04-27 13:34:55 -0700
committerPeter Collingbourne <peter@pcc.me.uk>2025-04-27 13:52:02 -0700
commitac2c00e10fe959190bfba685e9615527ef3c12f5 (patch)
tree7a5d05b46b5f6bf48819f0ed602b110bf0162ae8 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent5a1dd4fefb6dba2396e817482f19f4374d6b8e36 (diff)
gcc: stop passing --with-ld when cross compiling
Passing --with-ld causes problems when injecting a custom linker wrapper (similar to useMoldLinker) because it causes collect2 to check the --with-ld path (which is a hardcoded path to the standard linker wrapper) before $PATH, whereas with custom linker wrappers we want gcc to search $PATH. Because binutils-wrapper is not guaranteed to be present in $PATH, prepend it to $PATH in cc-wrapper. I verified that -print-prog-name=ld still prints an appropriate value. For example, when cross compiling for x86_64 on an aarch64 machine, the following is printed by the util-linux configure script (which uses -print-prog-name=ld [1]): checking for ld used by x86_64-unknown-linux-gnu-gcc... x86_64-unknown-linux-gnu-ld We still pass --with-as because the gcc spec file relies on this to find the assembler. This is probably fine for now as it is less common to want to override the assembler than the linker. [1] https://sources.debian.org/src/util-linux/2.41-4/m4/lib-ld.m4/?hl=59#L59
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions