* On 2025-01-05 at 17:57 GMT, Brook Milligan wrote:
Wip/gcc14 works for Darwin/x86_64 v24.
However, it does not build if libunwind is installed. Should there be a section like the following?
.if ${MACHINE_PLATFORM:MDarwin-*-x86_64}
CONFLICTS+= libunwind-[0-9]*
.endif
No, this would mean users could not install both gcc14 and libunwind, nor any of their dependents, on their systems at runtime, even though this is only a build-time issue.
In theory the wrappers should ensure that arbitrary libraries from LOCALBASE are not available to the compiler so it shouldn't matter if libunwind is installed or not, but as we've seen with e.g. cmake or when GCC is configured to look inside LOCALBASE, sometimes these measures can be circumvented.
Hopefully there is a configure variable that can be set to explicitly ignore any libunwind that is found. More details required on the actual failure mode here.
-- Jonathan Perkin pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com