Pass -no_fixup_chains to linker when required

[carlocab]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

Invoking ld with -undefined dynamic_lookup emits a warning starting
Xcode 14:

ld: warning: -undefined dynamic_lookup may not work with chained fixups

Chained fixups is a linker optimisation that results in faster binary
load times, and is enabled by default starting Xcode 13 when the target
is macOS 12 or newer.

However, this interacts poorly with -undefined dynamic_lookup, and
Xcode will disable chained fixups when it is invoked with this flag
starting Xcode 14.3. Until then, we may be shipping binaries that are
broken in subtle ways, so let's disable chained fixups when necessary
instead.

I patterned the changes here after the handling of -no_weak_imports.
The only difference is that we need to check the flags that were passed
to the linker first to see if we do need to disable chained fixups.

For additional context, see:

https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes
https://www.wwdcnotes.com/notes/wwdc22/110362/
https://www.emergetools.com/blog/posts/iOS15LaunchTime
python/cpython#97524
pybind/pybind11#4301

[BrewTestBot]

Review period will end on 2023-03-06 at 16:19:59 UTC.

[MikeMcQuaid]

Makes sense to me, nice work as usual @carlocab!

[Bo98]

Additionally, is there any concerns with this paired with -fuse-ld?

[carlocab]

Additionally, is there any concerns with this paired with -fuse-ld?

The only formula I'm aware of that uses this is v8, and that avoids the shims entirely. Still, I guess it would be useful to check for this. I added a check. It will produce some false positives, but it's a bit difficult to produce an airtight check given that you can pass arbitrary paths to -fuse-ld (with clang, at least).

[BrewTestBot]

Review period ended.

[Bo98]

Do we still get that xcrun stderr noise on I think 11-arm64?

[Bo98]

There is -version_details for better parsing (it's JSON) though it requires Xcode 10.2+.

Though with that said we could hardwire < Mojave to false which covers < 10.2.

[carlocab]

I think we still see a lot of xcrun stderr noise. Used -version_details instead, so we don't accidentally catch any stderr garbage.