Ryan Carsten Schmidt

The failure on macOS 14 is `ld: unknown options: -force_cpusubtype_ALL`. I'll need to patch that out.

I would prefer to fix the build failure rather than mark it known_fail. You needn't be the one to fix it; I can look into it. If there is a...

Yes, if you're distributing a binary to others, you want it to have the widest possible compatibility by using the oldest possible deployment target. Users building for their own use...

Specifically this is when using the configure argument `--enable-app`. It doesn't happen when using `--enable-lib-only`.

The `v` prefix does not add zero value. It indicates that the tag represents a released version. Tags can be used for any purpose, not just to denote released versions....

This appears to be installing a universal binary even when that was not requested. It needs to install only for the architectures MacPorts tells it to.

> The relation between the patch and the error message is unclear to me, > since the patch is focused on the `noexecstack` flags, while the error is on detecting...

> > The relation between the patch and the error message is unclear to me, > > since the patch is focused on the `noexecstack` flags, while the error is...

> The solution would be […] `EnableCompilerFlag` should be modified to prepend `LINKER:SHELL:` to the flag(s) when calling `CHECK_LINKER_FLAG` (but not when appending the flags to `CMAKE_EXE_LINKER_FLAGS` and `CMAKE_SHARED_LINKER_FLAGS`). Well,...

[So far](https://trac.macports.org/ticket/60511), the MacPorts default is to use X11. If you want to use native macOS rendering instead ([Quartz](https://en.wikipedia.org/wiki/Quartz_(graphics_layer))), uninstall all ports, add `+quartz` in /opt/local/etc/macports/variants.conf, and reinstall the ports...